Description of problem (please be detailed as possible and provide log snippests): Once the dr policy is applied to the application set type application, there is no way in UI to keep track of the last replication sync time(RPO). The last sync time is appearing on the dr status popover only after any dr action(failover / relocate) is triggered. Version of all relevant components (if applicable): 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)? 1 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. Apply DRPolicy to the application set type application on UI. Data services -> Data policies -> click DRPolicy action menu(three dots button) -> Manage policy for ApplicationSets -> move application from left to right -> enter PVC selector label using expand section -> click save. 2. Check the dr status popover on the Applications page. Applications -> Data policy column -> click policy href link 3. It won't show any information about the last sync time. 4. Trigger failover dr action. Application action menu(three dots) -> click Failover application -> click Initiate 5. Now you can see the last sync time. Actual results: The last sync time is hidden from the UI, it appears only when any dr action is triggered. Expected results: The last sync time should appear once the policy is applied to the application. Additional info:
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.13.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:3742
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days