Bug 1869359 - Q35 Fixups
Summary: Q35 Fixups
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ovirt-4.4.3
: 4.4.3.3
Assignee: Shmuel Melamud
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-17 17:00 UTC by Arik
Modified: 2020-11-11 06:49 UTC (History)
2 users (show)

Fixed In Version: ovirt-engine-4.4.3.2
Clone Of:
Environment:
Last Closed: 2020-11-11 06:42:27 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 110790 0 master MERGED core: Rename vm_static.bios_type field to custom_bios_type 2020-11-19 17:26:39 UTC
oVirt gerrit 110801 0 master MERGED webadmin: don't allow to reset chipset for cluster 2020-11-19 17:26:38 UTC

Description Arik 2020-08-17 17:00:13 UTC
This bz groups relatively small fixes that are needed in the context of Q35.

Comment 1 Arik 2020-09-13 08:57:42 UTC
This ended up in:
1. Rename CLUSTER-DEFAULT to AUTO-DETECT
2. Block the ability to reset bios-type that was already determined for a cluster back to CLUSTER-DEFAULT
3. Rename bios-type to Chipset/Firmware
4. Rename bios-type values

Comment 2 Nisim Simsolo 2020-10-26 14:43:43 UTC
Verified according to https://bugzilla.redhat.com/show_bug.cgi?id=1869359#c1

Verification builds:
ovirt-engine-4.4.3.7-0.22.el8ev
vdsm-4.40.34-1.el8ev.x86_64
libvirt-daemon-6.6.0-6.module+el8.3.0+8125+aefcf088.x86_64
qemu-kvm-5.1.0-13.module+el8.3.0+8382+afc3bbea.x86_64

Comment 3 Sandro Bonazzola 2020-11-11 06:42:27 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.


Note You need to log in before you can comment on or make changes to this bug.