-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
2.10.1
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
Description of problem:
When migrating a VM with an invalid rootDisk parameter (pointing to a partition that doesn't contain an OS), the migration succeeds but the resulting VM fails to boot. Virt-v2v does not validate that the selected partition actually contains an operating system.
Version-Release number of selected component (if applicable):
├── OCP version: 4.20.5 ├── MTV version: 2.10.1 (redhat-osbs-on-pr-43e196e4e358515ab86a8fcb630e65e64ad70505) └── CNV version: 4.20.3
How reproducible:
Always
Steps to Reproduce:
1. Create VMware vCenter provider (tested on vCenter 7.0.3) 2. Select a VM where rootDisk points to a non-OS partition (e.g., /dev/sdb1 or /dev/sdc1) 3. Perform migration
Actual results:
Migration succeeds Resulting VM fails to boot
Expected results:
Migration should fail or warn when the rootDisk does not contain a valid OS
Additional info:
Tested VM: miryam-win10- Windows Server 2019 Standard Provider: vCenter 7.0.3
