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

Registry overrides are being propagated to some data plane components

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • 4.16.0
    • 4.13, 4.12, 4.14, 4.15
    • HyperShift
    • Important
    • No
    • Hypershift Sprint 254, Hypershift Sprint 255, Hypershift Sprint 256
    • 3
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, registry overrides were present in non-relevant data plane images. With this release, the way {product-title} propagates the override-registries has been modified and the issue is fixed. (link:https://issues.redhat.com/browse/OCPBUGS-34602[*OCPBUGS-34602*])
      ____________
      *Cause*: Registry overrides are being propagated to some data plane components.
      *Consequence*: Registry overrides are present in non relevant data plane images.
      *Fix*: Modified the way we propagate the override-registries.
      *Result*: Bug doesn’t present anymore.
      Show
      * Previously, registry overrides were present in non-relevant data plane images. With this release, the way {product-title} propagates the override-registries has been modified and the issue is fixed. (link: https://issues.redhat.com/browse/OCPBUGS-34602 [* OCPBUGS-34602 *]) ____________ *Cause*: Registry overrides are being propagated to some data plane components. *Consequence*: Registry overrides are present in non relevant data plane images. *Fix*: Modified the way we propagate the override-registries. *Result*: Bug doesn’t present anymore.
    • Bug Fix
    • Done

      This is a clone of issue OCPBUGS-32257. The following is the description of the original issue:

      Description of problem:

      When using the registry-overrides flag to override registries for control plane components, it seems like the current implementation prpagates the override to some data plane components. 
      
      It seems that certain components like multus, dns, and ingress get values for their containers' images from env vars set in operators on the control plane (cno/dns operator/konnectivity), and hence also get the overridden registry propagated to them. 
      
      

      Version-Release number of selected component (if applicable):

          

      How reproducible:

          100%

      Steps to Reproduce:

          1.Input a registry override through the HyperShift Operator
          2.Check registry fields for components on data plane
          3.
          

      Actual results:

      Data plane components that get registry values from env vars set in dns-operator, ingress-operator, cluster-network-operator, and cluster-node-tuning-operator get overridden registries. 

      Expected results:

      overriden registries should not get propagated to data plane

      Additional info:

          

            agarcial@redhat.com Alberto Garcia Lamela
            openshift-crt-jira-prow OpenShift Prow Bot
            He Liu He Liu
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: