Description of problem: ----------------------- It's possible to run a warm migration plan with VMs that have CBT disabled. The plan doesn't progress. It would be good if we could catch this early and block such plans. The importer pod crashes with the “CrashLoopBackOff” status. Version-Release number of selected component (if applicable): ------------------------------------------------------------- MTV 2.0.0-17 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1.Create a warm migration plan with VMs that don't have CBT enabled. 2.Run the plan 3. Actual results: --------------- 1)While selecting VMs during plan creation, validator service correctly reports that VMs don't have CBT enabled and that enabling CBT is a prerequisite for for VM warm migration. 2)On the 'Migration type' page, the 'Warm migration' option is available and it's possible for users to successfully create a plan for warm migration with VMs that don't have CBT enabled. 3)The plan remains stuck after it is started.The importer pod crashes with the “CrashLoopBackOff” status. I0420 00:54:11.712313 1 importer.go:52] Starting importer I0420 00:54:11.713130 1 importer.go:134] begin import process I0420 00:54:11.713157 1 vddk-datasource.go:765] Creating VDDK data source: backingFile [[rhv-v2v-performance-testing] nachandr/nachandr-000001.vmdk], currentCheckpoint [snapshot-1351], previousCheckpoint [snapshot-1350], finalCheckpoint [false] I0420 00:54:11.766388 1 vddk-datasource.go:449] VM 4203c869-e3f7-cb78-3c2b-a50fae4edcf3 found in datacenter Datacenter:datacenter-2 @ /Datacenter: vm-1040 I0420 00:54:11.768037 1 vddk-datasource.go:310] Current VM power state: poweredOn E0420 00:54:11.782543 1 vddk-datasource.go:812] Unable to query changed areas: CBT is not enabled on disk 2000 I0420 00:54:11.782795 1 vddk-datasource.go:331] Logged out of VMware. E0420 00:54:11.782817 1 importer.go:172] CBT is not enabled on disk 2000 Expected results: ----------------- Prevent users from running a warm migration plan with VMs that have CBT disabled Additional info: ---------------- One way to do this would be to move the plan to 'Critical' state after creation and then moving the plan to 'Ready' once the issue has been fixed. Clicking on plan status should show that <VMs> don't have CBT enabled.
The fix should be in build 2.0.0-20 / iib:69034.
Verified on 2.0.0-20
Created attachment 1774237 [details] screenshot of a warm migration where a VM without CBT is skipped
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 (MTV 2.0.0 images), 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/RHEA-2021:2381