Bug 2059669 - [DR] Application namespace left behind in managed clusters after deleting the application
Summary: [DR] Application namespace left behind in managed clusters after deleting th...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ODF 4.17.0
Assignee: Shyamsundar
QA Contact: kmanohar
URL:
Whiteboard:
Depends On:
Blocks: 2281703 2056571
TreeView+ depends on / blocked
 
Reported: 2022-03-01 17:03 UTC by Sidhant Agrawal
Modified: 2024-10-30 14:25 UTC (History)
12 users (show)

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.
Clone Of:
Environment:
Last Closed: 2024-10-30 14:25:25 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github RamenDR ramen pull 1381 0 None open Delete manifestwork for application namespace 2024-09-05 21:12:37 UTC
Github red-hat-storage ramen pull 348 0 None open Bug 2059669: Delete manifestwork for application namespace 2024-09-07 12:12:28 UTC
Red Hat Product Errata RHSA-2024:8676 0 None None None 2024-10-30 14:25:39 UTC

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


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