Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1546

Using Shipwright in disconnected env.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • builds.1.5.1
    • None
    • Build, shipwright
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • With this fix, the correct images SHAs are updated and synced between the operator bundle and the build strategies. This fixes pulling the correct images in the disconnected cluster.
    • Bug Fix
    • Proposed

      Description of problem:

      Shipwright seems to be creating a `buildah` container inside the build pod but the buildah image used insn't in the release payload

      What are customer instructed to do when they use Shipwright in a disconnected env? Are they told to also manually mirror the buildah container image in addition to the release payload?

      Prerequisites (if any, like setup, operators/versions):

      A disconnected cluster

      Steps to Reproduce

      1. Have a disconnected cluster
      2. Run a Shipwright build
      3. If the user didn't mirror the buildah image - is the build pod failing to pull the image?

       

      Actual results:

      Expected results:

      Ideally, customer should not have any additional step in order to run disconnected envs. Usually they just mirror the release image, create an ITMS,IDMS,ICPS etc.

      Reproducibility (Always/Intermittent/Only Once):

      Acceptance criteria: 

       

      Definition of Done:

      Shipwright, or more specifically buildah, is available out of the box in a disconnected Openshift cluster.

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

              rh-ee-sabiswas Sayan Biswas
              ybettan@redhat.com Yoni Bettan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: