-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
None
-
2
-
False
-
None
-
False
-
-
-
-
MCO Sprint 24, SF Train-16, SF Train-17
-
No
Description of problem:
After unmanaging a cluster via ZTP by removing the siteconfig and resources file from gitops, the "open-cluster-management-addon-observability" namespace and objects running in the namespace are still there. I would expect all things to be cleaned up after a cluster is no longer managed by the hub.
# oc get managedcluster vm00002 Error from server (NotFound): managedclusters.cluster.open-cluster-management.io "vm00002" not found # oc --kubeconfig /root/hv-vm/kc/vm00002/kubeconfig get po -n open-cluster-management-addon-observability NAME READY STATUS RESTARTS AGE endpoint-observability-operator-b9bbddf88-kjq8w 1/1 Running 0 17m kube-state-metrics-d8bb96948-9xst4 3/3 Running 0 25h metrics-collector-deployment-74c75b47fb-2t4kb 1/1 Running 0 24m node-exporter-5b58n 0/2 Pending 0 25h prometheus-k8s-0 3/3 Running 0 25h prometheus-operator-7f5fff68b9-cd2r9 1/1 Running 0 25h
Version-Release number of selected component (if applicable):
ACM - 2.11.0-DOWNSTREAM-2024-05-23-15-16-26
Hub OCP - 4.16.0-rc.3
Deployed SNOs - 4.14.16
How reproducible:
Steps to Reproduce:
- ...
Actual results:
Expected results:
Additional info:
- is duplicated by
-
ACM-12178 ACM does not clean up resources from managedcluster when managedcluster is deleted via gitops
- Closed
- is related to
-
ACM-12178 ACM does not clean up resources from managedcluster when managedcluster is deleted via gitops
- Closed
- relates to
-
ACM-11962 ManagedCluster takes 5m to delete
- Closed