-
Bug
-
Resolution: Done
-
Undefined
-
ACM 2.11.0, ACM 2.8.4, ACM 2.9.4, ACM 2.10.3
-
False
-
None
-
False
-
-
-
Important
-
None
Description of problem:
When detaching a managed cluster from an ACM Hub cluster and executing the clean up steps from our Troubleshooting documentation we are still unable to re-import the new cluster due to issues with the Klusterlet not terminating successfully prior.
After running the cleanup steps to remove CRDs and CRs we see that all objects are removed but when the Klusterlet is recreated as a part of the manual cluster import flow we see that it comes up with a DeletionTimestamp and is unable to complete the setup process. It appears that because the finalizer is unable to complete we are leaving behind some artifacts that are causing the new import to fail.
Version-Release number of selected component (if applicable):
Seen on 2.8 and 2.10
How reproducible:
Occurs each time the klusterlet termination does not complete successfully
Steps to Reproduce:
- Detach ManagedCluster from Hub using manually cleanup steps from our Troubleshooting Documentation
- Attempt to re-import the ManagedCluster on a different Hub
Actual results:
Managed cluster fails to import, Klusterlet does not progress.
Expected results:
Managed cluster imports successfully, Klusterlet comes up clean.
Additional info: