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

Console deployment does not roll out when managed cluster configmap is updated


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 4.13.0
    • 4.10
    • Management Console
    • None

      Description of problem:

      There is a possible race condition in the console operator where the managed cluster config gets updated after the console deployment and doesn't trigger a rollout. 

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


      How reproducible:


      Steps to Reproduce:

      1. Enable multicluster tech preview by adding TechPreviewNoUpgrade featureSet to FeatureGate config. (NOTE THIS ACTION IS IRREVERSIBLE AND WILL MAKE THE CLUSTER UNUPGRADEABLE AND UNSUPPORTED) 
      2. Install ACM 2.5+
      3. Import a managed cluster using either the ACM console or the CLI
      4. Once that managed cluster is showing in the cluster dropdown, import a second managed cluster 

      Actual results:

      Sometimes the second managed cluster will never show up in the cluster dropdown

      Expected results:

      The second managed cluster eventually shows up in the cluster dropdown after a page refresh

      Additional info:

      Migrated from bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2055415

            rh-ee-jonjacks Jon Jackson
            rh-ee-jonjacks Jon Jackson
            YaDan Pei YaDan Pei
            0 Vote for this issue
            5 Start watching this issue