Bug 2209682 - RDR failover doesn't highlight sync policy and cannot failover in UI
Summary: RDR failover doesn't highlight sync policy and cannot failover in UI
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.12
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: gowtham
QA Contact: Prasad Desala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-24 13:41 UTC by rshah
Modified: 2023-08-09 16:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-21 06:34:35 UTC
Embargoed:


Attachments (Terms of Use)

Description rshah 2023-05-24 13:41:59 UTC
Description of problem (please be detailed as possible and provide log
snippests):

When I select RHACM to failover the application, the drsync policy is not highlighted and so cannot failover from the UI. 

This is intermittent issue. Not every lab deployed have this issue. Its like 1 in 10 labs I see this issue.

Version of all relevant components (if applicable):
OCP , ODF is 4.12 and RHACM is 2.7

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?
Might be to manually update the placement group yaml to failover and relocate, rather than using UI, but haven't tried this. 

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?

2

Can this issue reproducible?

Its intermittent issue, not reproducible as it doesn't occur in every lab.

Can this issue reproduce from the UI?
This is an UI issue, looks like the UI is not able to understand that there is drsync policy set for the concerned application and so it doesn't get highlighted to select drsync policy for failover..

If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info: If I capture an image, I will update it here.


Note You need to log in before you can comment on or make changes to this bug.