Bug 2062743

Summary:	Not able to delete multiclusterhub in rhacm 2.5
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	bjacot
Component:	unspecified	Assignee:	James Young <jayoung>
Status:	CLOSED DUPLICATE	QA Contact:	Eveline Cai <ecai>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhacm-2.5
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-10 13:33:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description bjacot 2022-03-10 13:30:44 UTC

Description of the problem:  Delete or cleaning up rhacm2.5 fails with finalizers.  I am not able to delete the multiclusterhub 

oc delete multiclusterhub --all -n "{{ rhacm_namespace }}"

Local-cluster namespace does not terminate.  Tried to manually delete the project and it failes with two finalizers

  - lastTransitionTime: "2022-03-10T13:11:58Z"
    message: 'Some resources are remaining: klusterletaddonconfigs.agent.open-cluster-management.io
      has 1 resource instances, managedclusteraddons.addon.open-cluster-management.io
      has 1 resource instances'
    reason: SomeResourcesRemain
    status: "True"
    type: NamespaceContentRemaining
  - lastTransitionTime: "2022-03-10T13:11:58Z"
    message: 'Some content in the namespace has finalizers remaining: agent.open-cluster-management.io/klusterletaddonconfig-cleanup
      in 1 resource instances, cluster.open-cluster-management.io/addon-pre-delete
      in 1 resource instances'
    reason: SomeFinalizersRemain
    status: "True"
    type: NamespaceFinalizersRemaining

Release version:
rhacm2.5

Operator snapshot version:
2.5.0-DOWNSTREAM-2022-03-07-12-45-01

Steps to reproduce:
1.  Install rhacm2.5
2.  Try to delete multiclusterhub


No workaround at this time.

Comment 1 bjacot 2022-03-10 13:33:53 UTC


*** This bug has been marked as a duplicate of bug 2061311 ***