Bug 2128074 - DR UI is not updating last data sync timestamp on Relocate and Failover modal
Summary: DR UI is not updating last data sync timestamp on Relocate and Failover modal
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: management-console
Version: 4.12
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ODF 4.12.0
Assignee: gowtham
QA Contact: Sidhant Agrawal
URL:
Whiteboard:
Depends On: 2132984
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-09-19 18:43 UTC by gowtham
Modified: 2023-08-09 16:46 UTC (History)
10 users (show)

Fixed In Version: 4.12.0-77
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-31 00:19:51 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-console pull 419 0 None open Fix last sync time for DR 2022-09-19 18:45:00 UTC
Github red-hat-storage odf-console pull 488 0 None open Bug 2132984: [release-4.12] Allow DR UI for the subsequent failover/relocate actions 2022-10-13 09:43:03 UTC
Github red-hat-storage odf-console pull 489 0 None open Bug 2132984: [release-4.12-compatibility] Allow DR UI for the subsequent failover/relocate actions 2022-10-13 09:43:03 UTC
Red Hat Product Errata RHBA-2023:0551 0 None None None 2023-01-31 00:20:12 UTC

Description gowtham 2022-09-19 18:43:42 UTC
Description of problem (please be detailed as possible and provide log
snippests):
From "All Cluster" view under the application list page, DR UI has an action called "Failover" and "Relocate". When the user clicks the action then it will display the modal with a list of options to select. There, "Data last synced on" is always showing "Unknown" status.

Version of all relevant components (if applicable):
ODF-Multicluster-Orchestrator - 4.12
OCP - 4.12
ACM - 2.6
ODF operator - 2.6

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?


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


Can this issue reproducible?
100%

Can this issue reproduce from the UI?
100%

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


Steps to Reproduce:
1. Follow the DR document up to apply the policy for the application.
2. Once Policy is applied then go to -> Application -> click action menu -> Failover / Relocate action.
3. From modal, Select DRPolicy, select Target Cluster, and select subscription groups(UI will auto-select)
4. UI has to display Least recent sync time from the selected subscription groups(here subscription group is nothing but the DRPC) Instead it displays Unknown.


Actual results:
"Data last synced on" is always showing "Unknown" status

Expected results:
"Data last synced on" should show the least recent sync time from the selected subscription group(i.e from selected DRPC)

Additional info:

Comment 17 errata-xmlrpc 2023-01-31 00:19:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenShift Data Foundation 4.12.0 enhancement and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:0551


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