Bug 2062743 - Not able to delete multiclusterhub in rhacm 2.5
Summary: Not able to delete multiclusterhub in rhacm 2.5
Keywords:
Status: CLOSED DUPLICATE of bug 2061311
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: unspecified
Version: rhacm-2.5
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: James Young
QA Contact: Eveline Cai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-10 13:30 UTC by bjacot
Modified: 2022-03-10 13:33 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 13:33:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.