-
Bug
-
Resolution: Done
-
Normal
-
ACM 2.11.2, MCE 2.6.2
-
None
-
2
-
False
-
None
-
False
-
-
-
SF Train-20, SF Train-21, SF Train-22
-
Moderate
-
None
Description of problem:
the cluster-proxy addon is stuck in the state "progressing... mca and work configs mismatch" for local-cluster
Version-Release number of selected component (if applicable):
2.11.2
How reproducible:
customer environment
Steps to Reproduce:
- apply custom cluster configuration in a 2.9 RHACM
- upgrade step by step to 2.11.2
- ...
Actual results:
cluster-proxy gets stuck in the state "progressing... mca and work configs mismatch"
Expected results:
post upgrade to 2.11.2, the cluster-proxy works
Additional info:
There was a deployment problem in 2.9 where https://access.redhat.com/solutions/7081139 was applied (in this situation, nodeselector configuration customization was added in the past)
the upgrade from 2.9 to 2.10.6 happened before the 2.11, less than an hour appart.
- is cloned by
-
ACM-14863 cluster-proxy addon stuck in state "progressing... mca and work configs mismatch"
- Closed
- links to
-
RHSA-2024:139901 Multicluster Engine for Kubernetes 2.6.4 security updates and bug fixes