Created attachment 2044376 [details]
acm failed with waitforreadiness logs

Description of problem (please be detailed as possible and provide log
snippests):
Failing over an ACM discovered VMWare VM - the pvc and secret a failed over but the vm is not. A different label is use in the vm and the pvc and secret

Version of all relevant components (if applicable):
OpenShift version 4.16.0-ec.5
odf-multicluster-orchestrator.v4.16.0-rhodf
ocs-client-operator.v4.16.0-rhodf
volsync-product.v0.10.0
OpenShift Virtualization 4.16.0
mtv-operator.v2.6.3
advanced-cluster-management.v2.11.1

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Failover of an ACM discovered VMWare VM imported via MTV stuck in WaitForReadiness state and does not reach WaitOnUserToCleanup status

Is there any workaround available to the best of your knowledge?
No

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?
yes

Can this issue reproduce from the UI?
yes

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

Steps to Reproduce:
1. Import a VMWare VM using MTV into the primary cluster c1
2. Label VM "name: vm", label pvc and secret "appname: vm" (different label used in vm, pvc and secret)
3. Access VM and write 2 small text files
4. Create and Enroll a protected application vmware2
5. Fence primary cluster c1
6. Fail over protected application vmware2 - 20 min later DRPC status still reporting WaitForReadiness and does not reach the WaitOnUserToCleanup state

Actual results:
Fail over protected application stuck reporting WaitForReadiness

Expected results:
Fail over protected application should reach WaitOnUserToCleanup status

Additional info:
oc get drpc -A -owide
NAMESPACE NAME AGE PREFERREDCLUSTER FAILOVERCLUSTER DESIREDSTATE CURRENTSTATE PROGRESSION START TIME DURATION PEER READY
openshift-dr-ops vmware2 5h59m c01-mdr-c1 c01-mdr-c2 Failover FailedOver WaitForReadiness 2024-08-18T13:51:04Z False