-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.14.z, 4.15.z, 4.17.z, 4.16.z
-
Low
-
Yes
-
1
-
T&PS 2024 #11, T&PS 2024 #12
-
2
-
False
-
-
-
Description of problem:
We are following the current documentation to remove a managed a cluster however it requires some manual steps (to run `oc delete managedcluster` command) to remove it. In the past our team raised an issue related to this one and now we see that documentation has been updated and it doesn't suggest to do any extra steps however that doesn't seem to be working with 4.16. Current documentation: https://docs.openshift.com/container-platform/4.16/edge_computing/ztp-deploying-far-edge-sites.html#ztp-site-cleanup_ztp-deploying-far-edge-sites The old issue that was raised and supposed to be fixed: https://issues.redhat.com/browse/OCPBUGS-18506
Version-Release number of selected component (if applicable):
4.16
How reproducible:
Very high frequency.
Steps to Reproduce:
1.Delete site from kustomization.yaml file. 2. 3.
Actual results:
Site not is deleted completely.
Expected results:
Site should be deleted completely.
Additional info:
The system impact of this issue would be that in the production this doesn't align with gitops principals.
- is related to
-
OCPBUGS-18506 ZTP/ACM: Remove a cluster from GitOps ZTP may require post-cleanup
- Closed
- links to
(2 links to)