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: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ODF 4.14.0
Assignee: rakesh
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-20 08:48 UTC by Aman Agrawal
Modified: 2023-08-16 11:00 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.