Bug 2059669

Summary: [DR] Application namespace left behind in managed clusters after deleting the application
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Sidhant Agrawal <sagrawal>
Component: odf-drAssignee: Shyamsundar <srangana>
odf-dr sub component: ramen QA Contact: kmanohar
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: edonnell, jpacker, kramdoss, madam, mmuench, muagarwa, ocs-bugs, odf-bz-bot, olakra, prsurve, sheggodu, srangana
Version: 4.10Keywords: Reopened
Target Milestone: ---   
Target Release: ODF 4.17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.17.0-95 Doc Type: Bug Fix
Doc Text:
.Application namespaces are no longer left behind in managed clusters after deleting the application Previously, if an application was deleted on the RHACM hub cluster and its corresponding namespace was deleted on the managed clusters, the namespace reappeared on the managed cluster. With this fix, once the corresponding namespace is deleted, the application no longer reappears.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2024-10-30 14:25:25 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:
Bug Depends On:    
Bug Blocks: 2281703, 2056571    

Description Sidhant Agrawal 2022-03-01 17:03:04 UTC 
Description of problem (please be detailed as possible and provide log
snippests):
Application namespace or project doesn't get deleted from managed clusters after deleting the application.
Other resources such as pods,pvc and backend rbd image gets deleted but leave the namespace behind.
Manual deletion also doesn't work as namespace is re-created in few seconds.

Version of all relevant components (if applicable):
OCP:  4.10.0-0.nightly-2022-02-26-230022
ODF: 4.10.0-171
ACM: 2.4.1

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
User impact: User will be unable to remove the namespace completely from the cluster

Is there any workaround available to the best of your knowledge?
NA

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:

Steps to Reproduce:
1. Configure RDR setup
2. Deploy workload
3. Do failover from C1 to C2
4. Delete the application using steps documented in [1]
5. Observe that the namespace or project doesn't get deleted

[1] https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.9/html-single/configuring_openshift_data_foundation_for_regional-dr_with_advanced_cluster_management#deleting-sample-application_rhodf


Actual results:
Application namespace left behind after deleting application.

Expected results:
Application namespace should be removed completely from the cluster.

Additional info:
Comment 7 Mudit Agarwal 2022-03-31 15:05:07 UTC 
Please add doc text
Comment 8 Shyamsundar 2022-04-05 16:29:58 UTC 
Provided required doc-text.
Comment 28 errata-xmlrpc 2024-10-30 14:25:25 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.17.0 Security, Enhancement, & Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:8676