Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1857148

Summary: OVA import (exported from the same 4.4 cluster) is not using the correct BIOS Type.
Product: [oVirt] ovirt-engine Reporter: Nisim Simsolo <nsimsolo>
Component: BLL.VirtAssignee: Shmuel Melamud <smelamud>
Status: CLOSED CURRENTRELEASE QA Contact: Nisim Simsolo <nsimsolo>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.1.8CC: ahadas, bugs, lrotenbe, nsimsolo, smelamud
Target Milestone: ovirt-4.4.3Flags: pm-rhel: ovirt-4.4+
Target Release: 4.4.3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.3.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-11 06:42:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1726558    
Bug Blocks:    
Attachments:
Description Flags
vdsm.log
none
engine.log
none
ovirt-export-ova-ansible
none
ovirt-import-ova-ansible none

Description Nisim Simsolo 2020-07-15 09:07:04 UTC
Description of problem:
Although BIOS type in exported OVF is correct (https://bugzilla.redhat.com/show_bug.cgi?id=1845458#c2) and the cluster compatibility version of the imported VM is the same as the cluster we import to, after importing the OVA, it will change to cluster default settings.

For example, after importing OVA of RHEL 8 with Q35 and SecureBoot BIOS type, to a clusetr with cluster default settings (Q35 with seabios)
The VM BIOS type will now be Q35 with seabios instead of Q35 with SecureBoot BIOS.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.1.8-0.7.el8ev
vdsm-4.40.22-1.el8ev.x86_64
libvirt-daemon-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64
qemu-kvm-4.2.0-29.module+el8.2.1+7297+a825794d.x86_64

How reproducible:
Alwayes

Steps to Reproduce:
1. Export VM (under default cluster with compatibility version 4.4) with Q35 and SecureBoot BIOS type as OVA
2. Import OVA to the same cluster.
3. Try to run VM.

Actual results:
VM BIOS type is now cluster default.
VM failed to boot from disk.

Expected results:
VM BIOS type should be equal to the one in OVF file.

Additional info:
vdsm.log, engine.log and OVA ansible logs attached (import started at 2020-07-15 09:40:44)

Comment 1 Nisim Simsolo 2020-07-15 09:12:52 UTC
Created attachment 1701179 [details]
vdsm.log

Comment 2 Nisim Simsolo 2020-07-15 09:13:14 UTC
Created attachment 1701180 [details]
engine.log

Comment 3 Nisim Simsolo 2020-07-15 09:14:01 UTC
Created attachment 1701181 [details]
ovirt-export-ova-ansible

Comment 4 Nisim Simsolo 2020-07-15 09:14:27 UTC
Created attachment 1701182 [details]
ovirt-import-ova-ansible

Comment 5 Arik 2020-07-15 09:25:21 UTC
Should be solved by the fix for bz 1855001, not closing as duplicate because it's a bit different flow (OVA rather than v2v)

Comment 6 Nisim Simsolo 2020-09-10 07:47:03 UTC
Reassigned:
ovirt-engine-4.4.2.4-0.1.el8ev
vdsm-4.40.26.1-1.el8ev.x86_64
libvirt-daemon-6.0.0-25.2.module+el8.2.1+7722+a9e38cf3.x86_64
qemu-kvm-4.2.0-29.module+el8.2.1+7712+3c3fe332.2.x86_64

Reason:
Same behavior as described in https://bugzilla.redhat.com/show_bug.cgi?id=1857148#c0

Comparing domxml of imported VM (from OVA) to source VM (exported as OVA):
Imported:
 <os>
    <type arch='x86_64' machine='pc-q35-rhel8.2.0'>hvm</type>
    <smbios mode='sysinfo'/>
  </os>

Source VM:
<os>
    <type arch='x86_64' machine='pc-q35-rhel8.2.0'>hvm</type>
    <loader readonly='yes' secure='yes' type='pflash'>/usr/share/OVMF/OVMF_CODE.secboot.fd</loader>
    <nvram template='/usr/share/OVMF/OVMF_VARS.secboot.fd'>/var/lib/libvirt/qemu/nvram/1abede2e-d49c-4f48-bf63-fbcc80ab33df.fd</nvram>
    <smbios mode='sysinfo'/>
  </os>

Comment 7 Shmuel Melamud 2020-09-10 11:13:55 UTC
(In reply to Nisim Simsolo from comment #6)

Did the Engine build contain this change https://gerrit.ovirt.org/#/c/110880/ ? I've just tested exporting/importing a SecureBoot VM with it and the result is correct.

Comment 8 Nisim Simsolo 2020-09-10 11:42:24 UTC
(In reply to Shmuel Melamud from comment #7)
> (In reply to Nisim Simsolo from comment #6)
> 
> Did the Engine build contain this change
> https://gerrit.ovirt.org/#/c/110880/ ? I've just tested exporting/importing
> a SecureBoot VM with it and the result is correct.

In which engine build does this change included?

Comment 9 Arik 2020-09-10 15:16:50 UTC
ok, so this bug shouldn't have switched to on_qa as it depends on bz 1726558, switching back to modified

Comment 11 Nisim Simsolo 2020-10-05 09:19:26 UTC
Verified:
ovirt-engine-4.4.3.5-0.5.el8ev
qemu-kvm-5.1.0-10.module+el8.3.0+8254+568ca30d.x86_64
vdsm-4.40.32-1.el8ev.x86_64
libvirt-daemon-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64

Comment 12 Sandro Bonazzola 2020-11-11 06:42:29 UTC
This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.