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

Bug 1952787

Summary: Chipset/firmware type setting doesn't work when creating vm pool
Product: [oVirt] ovirt-engine Reporter: Qin Yuan <qiyuan>
Component: GeneralAssignee: Lucia Jelinkova <ljelinko>
Status: CLOSED CURRENTRELEASE QA Contact: Qin Yuan <qiyuan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.6.5CC: ahadas, bugs, dfodor, mjurasek
Target Milestone: ovirt-4.4.6Keywords: Automation, Regression
Target Release: ---Flags: pm-rhel: ovirt-4.4+
mjurasek: blocker+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.6.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-05 05:36:21 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:

Description Qin Yuan 2021-04-23 06:53:41 UTC
Description of problem:
When creating vm pool, the Chipset/Firmware Type setting doesn't take effect, the created pool's actual Chipset/Firmware Type is different from the setting value.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.6.5-0.17.el8ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Prepare Cluster and VM template:
   - Cluster's compatibility version is 4.6, Chipset/Firmware Type is Q35 Chipset with BIOS
   - The VM template's Chipset/Firmware Type is Q35 Chipset with BIOS(the test used latest-rhel-guest-image-8.3-infra)

2. Create VM pool:
   - Cluster: the prepared Cluster
   - Template: the prepared template
   - Number of VMs: 1
   - Prestarted VMs: 0
   - Maximum number of VMs per user: 1
   - Chipset/Firmware Type: select one of the following values,
     I440FX Chipset with BIOS
     Q35 Chipset with UEFI
     Q35 Chipset with UEFI SecureBoot

3. Check the VM pool's Chipset/Firmware Type after it's created.


Actual results:
1. VM pool's actual Chipset/Firmware Type is always Q35 Chipset with BIOS, regardless which type is set at the time of creation.

Expected results:
1. VM pool's actual Chipset/Firmware Type should be the same as the value selected when creating the pool.

Additional info:

Comment 1 RHEL Program Management 2021-04-26 11:18:47 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 2 Qin Yuan 2021-04-30 04:14:04 UTC
Verified with:
ovirt-engine-4.4.6.6-0.10.el8ev.noarch

Steps:
The same as steps in Bug Description.

Results:
VM pool's actual Chipset/Firmware Type is the same as the value selected when creating the pool.

Comment 3 Sandro Bonazzola 2021-05-05 05:36:21 UTC
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.6 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.