Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-43307

After upgrading to OCP 4.16 Builds fail, if push secret is not explicitly defined in BuildConfig

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 4.16
    • Build
    • Yes
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      After upgrading to OCP 4.16, the push secret *to an external container registry*has to be explicitly defined in the buildconfig yaml for it to succeed. The associated push secret with the builder Service Account is not selected automatically.

      Workaround: Specify the secret used for pushing the container image in the BuildConfig

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

      OpenShift 4.16

      Steps to Reproduce

      1.  Create a buildconfig that pushes to an external container registry, such as quay.io.
      2. Link the push secret to builder SA using the oc command line
      3.  Do not specify the push secret explicitly in buildconfig yaml
      4. The build fails to push the image with, with failure to connect to the registry

       

      Actual results:

      The secret associated with builder SA is not selected and has to be specified explicitly in buildconfig yaml for builds to succeed.
       

      Expected results:

      The correct push secret associated with builder SA should be selected automatically.{}

      Reproducibility (Always/Intermittent/Only Once):

      Always in OCP 4.16

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

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

       

       *

              rh-ee-sabiswas Sayan Biswas
              rhn-support-jyarora Jyotsana Arora
              Jyotsana Arora
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: