-
Bug
-
Resolution: Done
-
Blocker
-
MCE 2.5.3
-
None
-
3
-
False
-
None
-
False
-
-
-
SF Train-16
-
Critical
-
Customer Escalated, Customer Facing
-
+
-
Yes
Description of problem:
Local cluster and 1 other cluster (an hcp cluster) went into unknown status
Version-Release number of selected component (if applicable):
2.10.3
How reproducible:
Steps to Reproduce:
- ...
Actual results:
Expected results:
Additional info:
The 2 affected clusters only have 1 klusterlet agent pods instead of 3. Tried to delete the import secret and then re-apply the new import secret on the local-cluster and did not seem to work.
- links to
-
RHBA-2024:135610 Multicluster Engine for Kubernetes 2.5.5 bug fix updates
- mentioned on