Description of problem (please be detailed as possible and provide log snippests): [RDR] When performing cross cluster failover of 2 apps cleanup of app-1 is stuck and failover of app-2 is stuck Version of all relevant components (if applicable): OCP version:- 4.13.0-0.nightly-2023-05-11-225357 ODF version:- 4.13.0-199 CEPH version:- ceph version 17.2.6-47.el9cp (6add4f24d1eff88e1db808ecdc16fd5b2db96dd4) quincy (stable) ACM version:- 2.8.0-169 SUBMARINER version:- v0.15.0 VOLSYNC version:- volsync-product.v0.7.1 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? yes 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? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1.Deploy RDR cluster 2.Deploy app-1 over c1 and deploy app-2 over c2 3. Perform failover of both the apps ie app-1 -> c2 and app-2 ->c1 Actual results: PVC are stuck in termination state oc get drpc -A -o wide NAMESPACE NAME AGE PREFERREDCLUSTER FAILOVERCLUSTER DESIREDSTATE CURRENTSTATE PROGRESSION START TIME DURATION PEER READY openshift-gitops busybox-1-placement-drpc 46h prsurve-c1 prsurve-vm-d Failover FailedOver Cleaning Up 2023-05-16T12:44:10Z True openshift-gitops busybox-2-kernel-placement-drpc 2d1h prsurve-c1 Relocate Relocated Completed 2023-05-16T10:32:57Z 10m19.27439987s True openshift-gitops busybox-8-placement-drpc 2d2h prsurve-c1 prsurve-c1 Failover FailingOver WaitingForResourceRestore 2023-05-16T12:44:04Z False Expected results: Additional info:
Not a 4.13 blocker, adding it as a known issue. @srangana please fill the doc text.