Bug 2305603 - [CNV][MDR] VM not failed over and in WaitForReadiness status
Summary: [CNV][MDR] VM not failed over and in WaitForReadiness status
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nir Soffer
QA Contact: krishnaram Karthick
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-08-18 20:20 UTC by Kevin Alon Goldblatt
Modified: 2024-09-16 13:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OCSBZM-8816 0 None None None 2024-08-21 13:45:37 UTC

Description Kevin Alon Goldblatt 2024-08-18 20:20:19 UTC
Created attachment 2044376 [details]
acm failed with waitforreadiness logs

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


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