-
Bug
-
Resolution: Duplicate
-
Blocker
-
2.11.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
Description of problem:
Migrate windows VM from OVA file to OCP cluster, the VM failed to boot, hit error: "No bootable device"

Version-Release number of selected component (if applicable):
MTV 2.11.0-45 with CNV 4.21.1 or MTV 2.11.0-45 with CNV 4.20.5
How reproducible:
Always
Steps to Reproduce:
1) Set Forklift Controller FC: feature_ova_appliance_management: 'true', create ova provider with applianceManagement: true
2) Create ova provider: ova-test
3) Create migration plan: ova-test-win2019 to migrate VM: auto-esx8.0-win2019-efi-with-extra-online-disks from ova provider to OCP 4.21 cluster
4) The plan executed successfully
5) The VM failed to boot, hit error: "No bootable device", more details in attached files: plan-ova-test-win2019.yaml, vm-auto-esx8.0-win2019-efi-with-extra-online-disks-yaml
6) Checked the VM first disk is vol-0, PVC: "ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-57f9h", this PVC is the one with OS,
thus it's more likely the data is loss.
$ oc get pvc|grep ova-test-win2019
ova-store-pvc-ova-test-ova-test-win2019-6wwfx Bound ova-store-pv-ova-test-ova-test-win2019-98gp5 1Gi ROX <unset> 43m
ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-57f9h Bound pvc-7cfccf43-01ba-450d-bb72-9920673d285e 68289980007 RWX nfs-csi <unset> 43m
ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-7nxwx Bound pvc-64bd64eb-3e08-4c32-b1aa-e4c4f80c70c4 4552665334 RWX nfs-csi <unset> 43m
ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-87cd6 Bound pvc-645b3496-f240-4556-bd2a-33ba6f822281 6828998001 RWX nfs-csi <unset> 43m
ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-fk9p4 Bound pvc-a9593831-ad40-4a12-9912-955692e633f4 2276332667 RWX nfs-csi <unset> 43m
$ oc get vm auto-esx8.0-win2019-efi-with-extra-online-disks -o yaml
devices:
disks:
- disk:
bus: virtio
name: vol-0
- disk:
bus: virtio
name: vol-1
- disk:
bus: virtio
name: vol-2
- disk:
bus: virtio
name: vol-3
volumes:
- name: vol-0
persistentVolumeClaim:
claimName: ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-57f9h
- name: vol-1
persistentVolumeClaim:
claimName: ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-fk9p4
- name: vol-2
persistentVolumeClaim:
claimName: ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-7nxwx
- name: vol-3
persistentVolumeClaim:
claimName: ova-test-win2019-7bffb6e899446ed10721a75f32297b2b4b18-87cd6
Actual results:
In step5: The VM failed to boot
Expected results:
In step5: The VM is boot successfully
Additional info:
- impacts account
-
MTV-4497 OVA migration changes firmware from EFI to BIOS causing boot failure
-
- MODIFIED
-