This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2219460 - [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
Summary: [RFE] Raise a warning pop-up (dialog box) when failover/relocate operation is...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.13
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: gowtham
QA Contact: Aman Agrawal
URL:
Whiteboard:
: 2134052 2221920 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-03 19:07 UTC by Aman Agrawal
Modified: 2024-05-17 11:21 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-05-17 10:06:13 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHSTOR-5895 0 None None None 2024-05-17 11:20:59 UTC

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