-
Bug
-
Resolution: Unresolved
-
Major
-
2.9.0
-
Quality / Stability / Reliability
-
False
-
-
True
-
-
-
MTV Sprint 4
Description of problem:
Create a cold,warm migration plan to migrate 2 VMs: nvme VM: mtv-func-win2022-nvme, and VM: mtv-func-rhel8-multi-nics, hit the expected critical concerns when select VMs, continue to create and execute the plan, the migration for nvme disk hang, the plan hang
Version-Release number of selected component (if applicable):
MTV 2.9.0(forklift-fbc-prod-v418:on-pr-16546d253dda4fc8d8b838f0703040f30a985cf0) with CNV 4.18.7
How reproducible:
Always
Steps to Reproduce:
1) Create a cold migration plan to migrate VMs: nvme VM: mtv-func-win2022-nvme, and VM: mtv-func-rhel8-multi-nics, hit the expected critical concerns when select VMs
2) Click "Confirm selections" to create the plan
3) The plan status is "Ready for migration", no error in the "Plan Details" page, start the migration
4) Check the migration for VM: mtv-func-rhel8-multi-nics is succeeded, the migration for VM: mtv-func-win2022-nvme is hang after "Disk Allocation" phase, no "Migration Resources" is listed, and the migration plan is keep on Running, the forklift-controller pod log: forklift-controller-5bbb448f79-w4gcb-main.log
Actual results:
Step4: The migration for VM with nvme disk is hang, the plan is hang
Expected results:
Step2: The migration for VM with nvme disk is failed as not supported currently, the plan is not hang