Created attachment 1985681 [details] Screenshot showing the issue Description of problem (please be detailed as possible and provide log snippests): When trying to relocate or failover a new application with assigned dr policy, the dialog sometimes show wrong error a bout missing drpolicy. (!) No DRPolicy found Closing the dialog and trying again typically fixes the issue. When this happens, the application is running and protected by ramen, having a drpc in Completed phase. This is not a timing issue, can happen minutes after the drpolicy was assigned. Version of all relevant components (if applicable): OpenShift version: 4.13.8 advanced-cluster-management: v2.8.0 multicluster-engine: v2.3.0 odf-multicluster-orchestrator: v4.13.2-rhodf odr-hub-operator: v4.13.2-rhodf Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No, retrying is easy Is there any workaround available to the best of your knowledge? Unknown 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? Easy to reproduce, fail about 40% of times Can this issue reproduce from the UI? Yes Steps to Reproduce: 1. Create subscription based application using busybox-ord-cephfs but seen also with busybox-odr (using rbd) 2. Wait until the application is up on the cluster 3. Assign drpolicy 4. Wait until the drpc is finished: phase: completed lastSyncGroupTime: not empty 5. Open the application page and select the "Relocate" or "Failover" item from the menu. Actual results: Randomly getting "DRPolicy not found" error Expected results: No error as drpolicy is assigned and used by the system.
In some cases retrying once is not enough, but after 4-5 retries the error is gone.
Not seen "DRPolicy not found" error when the failover/relocation modal is opened from the Application Details page and when the failover/relocate modal is opened from the Application List. PFA screenshot for reference. Hence marking it as verified. Product versions- ODF- 4.14.0-139 OCP- 4.14.0
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 (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & 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/RHSA-2023:6832
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days