Description of the problem: Updated the MCIR with the appropriate registries, the 4.x clusters picked up the change and are working as expected. The 3.11 clusters however have not picked up the change and are still in CrashLoopBackoff. Release version: 2.5 Operator snapshot version: OCP version: 3.11 Browser Info: Steps to reproduce: 1. Attach 3.11 cluster to a hub using the MCIR settings from 2.4 2. Upgrade ACM from 2.4 to 2.5 3. Modify MCIR with the registries in 2.5 docs Actual results: 3.11 clusters do not pick up the change and remain in Expected results: 3.11 clusters behave the same as 4.x and pick up the MCIR change Additional info: 2.4 MCIR docs https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.4/html/clusters/managing-your-clusters#imp[…]ride 2.5 MCIR docs https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5/html/clusters/managing-your-clusters#imp[…]ride
could you help collect some info? or the mce and mch must-gather will be best. oc get placements.cluster.open-cluster-management.io -A -o yaml oc get placementdecisions.cluster.open-cluster-management.io -A -o yaml oc get managedclusterset -o yaml oc get mcl -o yaml oc get managedclusterimageregistries.imageregistry.open-cluster-management.io -A -o yaml oc get managedclusteraddons.addon.open-cluster-management.io -A -o yaml oc get manifestworks.work.open-cluster-management.io -A -o yaml
from the logs the cluster dmzsecuretestrr2 is not selected by the placement used in ManagedClusterImageRegistry. because the cluster has a taint taints: - effect: NoSelect key: cluster.open-cluster-management.io/unreachable timeAdded: null in 2.5, the placement used in ManagedClusterImageRegistry should add a toleration in the spec: tolerations: - key: "cluster.open-cluster-management.io/unreachable" operator: Exists please refer to the section 1.7.3.1 step 2 in the doc https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.5/html/clusters/managing-your-clusters#imp-clust-custom-image-override
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Critical: Red Hat Advanced Cluster Management 2.5.2 security fixes and bug fixes), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:6507
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days