Bug 1824472 - Default cluster has wrong bios type
Summary: Default cluster has wrong bios type
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.4.0
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: ovirt-4.4.0
: ---
Assignee: Shmuel Melamud
QA Contact: Nisim Simsolo
URL:
Whiteboard:
Depends On:
Blocks: 1823674
TreeView+ depends on / blocked
 
Reported: 2020-04-16 09:42 UTC by Michal Skrivanek
Modified: 2020-05-20 20:00 UTC (History)
5 users (show)

Fixed In Version: ovirt-engine-4.4.0_beta4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-20 20:00:19 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.4+
rbarry: blocker?


Attachments (Terms of Use)
Screenshot of edit cluster dialog (152.01 KB, image/png)
2020-04-19 12:31 UTC, Nisim Simsolo
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 108410 0 master ABANDONED core: Fixed Bios Type Upgrade on VM 2020-08-03 16:58:47 UTC
oVirt gerrit 108412 0 master MERGED core: Change cluster 'Default' initial column values 2020-08-03 16:58:46 UTC
oVirt gerrit 108418 0 master MERGED core: Change initial default of cluster.bios_type 2020-08-03 16:58:46 UTC
oVirt gerrit 108420 0 master MERGED core: Remove unnecessary change to cluster table 2020-08-03 16:58:47 UTC

Description Michal Skrivanek 2020-04-16 09:42:18 UTC
"Default" cluster is still created in a wrong way, it has bios_type "1" in db

Comment 1 Michal Skrivanek 2020-04-16 10:19:41 UTC
also the ballooning is disabled. It's enabled for any other normal cluster since..4.0 or so. Please fix that for the Default cluster too.

Comment 2 Nisim Simsolo 2020-04-19 12:28:38 UTC
Reassigned:
1. In WebAdmin, edit cluster dialog, the BIOS type is grayed out (cannot be selected).
2. BIOS type value is set to "Cluster Default" without any reference to what "cluster Default" stands for.

this issues are relevant for default cluster and new cluster.

Builds:
ovirt-engine-4.4.0-0.33.master.el8ev
vdsm-4.40.13-1.el8ev.x86_64

Comment 3 Nisim Simsolo 2020-04-19 12:31:13 UTC
Created attachment 1680014 [details]
Screenshot of edit cluster dialog

Comment 4 Dominik Holler 2020-04-20 13:40:58 UTC
Can this bug changed to MODIFIED?

Comment 5 Michal Skrivanek 2020-04-20 13:41:56 UTC
(In reply to Nisim Simsolo from comment #2)
> Reassigned:
> 1. In WebAdmin, edit cluster dialog, the BIOS type is grayed out (cannot be
> selected).
> 2. BIOS type value is set to "Cluster Default" without any reference to what
> "cluster Default" stands for.

and that's a correct behavior, since you don't have architecture or cpu determined yet


what matters is that it's set correctly once you add a host

Comment 6 Nisim Simsolo 2020-04-21 07:37:04 UTC
Verified: 
ovirt-engine-4.4.0-0.33.master.el8ev
vdsm-4.40.13-1.el8ev.x86_64
qemu-kvm-4.2.0-19.module+el8.2.0+6296+6b821950.x86_64
libvirt-daemon-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64

Verification scenario:
1. Add host to "Default" cluster.
   Verify the next:
   - in engine db, bios_type=2 and enable_balloon=t
   for example:
   engine=# select enable_balloon,bios_type from cluster where name='Default';
   enable_balloon | bios_type 
   ----------------+-----------
    t              |         2

   - Browse WebAdmin -> Compute -> Clusters, open Default cluster edit dialog
   BIOS type dropbox is wth the next value: "Q35 Chipset with Legacy BIOS"
   and it is possible to drop down dropbox and select other values.

2. Create new DC, New Cluster and add host to the new cluster.
   Verify the next:
   - in engine db, bios_type=2 and enable_balloon=f
   For example:
   engine=# select enable_balloon,bios_type from cluster where name='new_cluster';
   enable_balloon | bios_type 
   ----------------+-----------
    f              |         2

   - Browse WebAdmin -> Compute -> Clusters, open Default cluster edit dialog
   BIOS type dropbox is wth the next value: "Q35 Chipset with Legacy BIOS"
   and it is possible to drop down dropbox and select other values.

Comment 7 Sandro Bonazzola 2020-05-20 20:00:19 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

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