Bug 2219460

Summary:	[RFE] Raise a warning pop-up (dialog box) when failover/relocate operation is triggered where lastGroupSyncTime is either missing or is 2x or more behind sync interval
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Aman Agrawal <amagrawa>
Component:	management-console	Assignee:	gowtham <gshanmug>
Status:	CLOSED MIGRATED	QA Contact:	Aman Agrawal <amagrawa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	ckumar, dkamboj, gshanmug, nberry, odf-bz-bot, sheggodu, skatiyar, srangana
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
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:	2024-05-17 10:06:13 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:

Comment 14 Chandan 2023-07-26 12:29:47 UTC

What implications would a lagging sync interval have over failover/relocate actions? 

Assuming sync is delayed and there is a need to failover/relocate what options does the user have? 

Do we stop users from performing failover/relocate, is it even possible to stop users? Could they correct things before proceeding to perform failover/relocate? 

In case we allow users to continue with failover by displaying a warning what outcomes could users expect to see after the actions complete?

Comment 15 Aman Agrawal 2023-07-26 14:37:42 UTC

(In reply to Chandan from comment #14)
> What implications would a lagging sync interval have over failover/relocate
> actions? 
> 
> Assuming sync is delayed and there is a need to failover/relocate what
> options does the user have? 
> 
> Do we stop users from performing failover/relocate, is it even possible to
> stop users? Could they correct things before proceeding to perform
> failover/relocate? 
> 
> In case we allow users to continue with failover by displaying a warning
> what outcomes could users expect to see after the actions complete?

Feel free to setup a meeting and include all required stakeholders to discuss further.

Comment 16 gowtham 2023-07-31 07:13:01 UTC

(In reply to Chandan from comment #14)
> What implications would a lagging sync interval have over failover/relocate
> actions? 
> 
> Assuming sync is delayed and there is a need to failover/relocate what
> options does the user have? 
> 
> Do we stop users from performing failover/relocate, is it even possible to
> stop users? Could they correct things before proceeding to perform
> failover/relocate? 
> 
> In case we allow users to continue with failover by displaying a warning
> what outcomes could users expect to see after the actions complete?

Adding more the Chandan doubts:
  - We are also supporting CLI-based implementation, What if the user trigger failover/relocates from CLI? 
  - Assume this sync delay is happening and After some time cluster is down, User dont have a choice other than failover, how does this dialogue box will help?

Comment 18 Aman Agrawal 2023-08-02 07:28:02 UTC

*** Bug 2134052 has been marked as a duplicate of this bug. ***

Comment 23 Shyamsundar 2024-01-09 13:11:57 UTC

*** Bug 2221920 has been marked as a duplicate of this bug. ***

Comment 24 Sanjal Katiyar 2024-01-17 08:50:49 UTC

both backend and UX discussions are required, moving to 4.16 for now...