Bug 2136413 - [RDR] [UI] When DRPC is deleted from the local-cluster via UI, it doesn't provide deletion status/progress
Summary: [RDR] [UI] When DRPC is deleted from the local-cluster via UI, it doesn't pro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.12
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ODF 4.16.0
Assignee: rakesh-gm
QA Contact: Sidhant Agrawal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-20 08:48 UTC by Aman Agrawal
Modified: 2024-07-17 13:10 UTC (History)
9 users (show)

Fixed In Version: 4.16.0-94
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-07-17 13:10:37 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ramen pull 122 0 None open Bug 2136413: drpc: add deletion progression status 2023-08-22 11:25:30 UTC
Red Hat Product Errata RHSA-2024:4591 0 None None None 2024-07-17 13:10:41 UTC

Comment 3 Debjyoti Pandit 2022-10-31 08:26:03 UTC 
Checked from the OLM side, if we are reporting proper status. It will get displayed.
And also from the CLI side, the CR is getting deleted without moving to terminating state.
The CR is not reporting the status change properly. Once the CR is deleted, it needs to move to terminating state from the deployed state. 
Currently, it is directly getting deleted.
Comment 5 Shyamsundar 2022-11-02 18:25:40 UTC 
(In reply to Debjyoti Pandit from comment #3)
> Checked from the OLM side, if we are reporting proper status. It will get
> displayed.
> And also from the CLI side, the CR is getting deleted without moving to
> terminating state.
> The CR is not reporting the status change properly. Once the CR is deleted,
> it needs to move to terminating state from the deployed state. 
> Currently, it is directly getting deleted.

I am unable to parse the requirement/problem here. A deleted CR will linger around till all finalizers are cleaned up at which point the CR is deleted from the API server. Which field/status is expected to go to Terminating etc. for this to work?
Comment 6 Debjyoti Pandit 2022-11-03 09:38:39 UTC 
(In reply to Shyamsundar from comment #5)
> (In reply to Debjyoti Pandit from comment #3)
> > Checked from the OLM side, if we are reporting proper status. It will get
> > displayed.
> > And also from the CLI side, the CR is getting deleted without moving to
> > terminating state.
> > The CR is not reporting the status change properly. Once the CR is deleted,
> > it needs to move to terminating state from the deployed state. 
> > Currently, it is directly getting deleted.
> 
> I am unable to parse the requirement/problem here. A deleted CR will linger
> around till all finalizers are cleaned up at which point the CR is deleted
> from the API server. Which field/status is expected to go to Terminating
> etc. for this to work?

The issue is that when the deleted CR lingers during the clean-up process, the status stays in the deployed state.
Instead, it should move to terminating state or any other signifying that we have deleted already the CR.
Comment 29 Aman Agrawal 2023-10-10 12:29:24 UTC 
Not a 4.14 blocker, moving out.
Comment 43 errata-xmlrpc 2024-07-17 13:10:37 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.16.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:4591
Note You need to log in before you can comment on or make changes to this bug.