Bug 2136413

Summary:	[RDR] [UI] When DRPC is deleted from the local-cluster via UI, it doesn't provide deletion status/progress
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Aman Agrawal <amagrawa>
Component:	odf-dr	Assignee:	rakesh <rgowdege>
odf-dr sub component:	ramen	QA Contact:	krishnaram Karthick <kramdoss>
Status:	ASSIGNED ---	Docs Contact:
Severity:	low
Priority:	unspecified	CC:	dpandit, gshanmug, jefbrown, muagarwa, nthomas, odf-bz-bot, rgowdege, rtalur, skatiyar, srangana
Version:	4.12
Target Milestone:	---
Target Release:	ODF 4.14.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

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.