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

Bug 1852040

Summary:	After 4.3 to 4.4 upgrade it's impossible to create new VMs in existing clusters
Product:	[oVirt] ovirt-engine	Reporter:	Lev Veyde <lveyde>
Component:	BLL.Virt	Assignee:	Lev Veyde <lveyde>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.4.1.4	CC:	ahadas, bugs, csiga, khakimi, michal.skrivanek, sbonazzo, smelamud
Target Milestone:	ovirt-4.4.1	Keywords:	Triaged
Target Release:	4.4.1.5	Flags:	pm-rhel: ovirt-4.4+
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.1.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-08 08:26:31 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 Lev Veyde 2020-06-29 16:05:09 UTC

Description of problem:
Following a successful 4.3 to 4.4 upgrade it's impossible to create a new VM(s) in the existing clusters.


Version-Release number of selected component (if applicable):
4.4.1.4

How reproducible:
100%

Steps to Reproduce:
1. Upgrade an existing oVirt/RHV 4.3 env. to 4.4
2. Following the upgrade attempt to create a new VM in the existing cluster.
3. The creation attempt will fail without an error - clicking on OK button in the Create new VM dialog will do nothing.

Actual results:
It's impossible to create new VM.

Expected results:
It should be possible to create new VM(s) on existing clusters.

Additional info:
The workaround exists:
Customer needs to manually edit each of the existing clusters and modify the "BIOS Type" from "Cluster Default" to "Legacy".

Comment 1 Arik 2020-06-29 16:38:17 UTC

Shmuel, how about an upgrade script that changes clusters with bios-type=CLUSTER_DEFAULT to Legacy?

Comment 2 Michal Skrivanek 2020-06-30 03:12:55 UTC

But they are not being executed on restore, are they?

Comment 3 Arik 2020-06-30 06:50:04 UTC

I think they must be executed, otherwise how would the bios_type be added to clusters?

And minor addition to comment 1 - we also need to check whether the cluster is not empty (in terms of hosts) in order to prevent the Default cluster being changed on new deployments (not upgrades).

Comment 4 Michal Skrivanek 2020-06-30 07:47:42 UTC

*** Bug 1852020 has been marked as a duplicate of this bug. ***

Comment 5 Michal Skrivanek 2020-06-30 07:49:40 UTC

it's probably nicer to treat them as if they would be newly created. It's not such a common case, and we say "existing cluster are not going to be changed"....so not too important

Comment 6 Lev Veyde 2020-06-30 08:45:11 UTC

(In reply to Arik from comment #3)
> I think they must be executed, otherwise how would the bios_type be added to
> clusters?
> 
> And minor addition to comment 1 - we also need to check whether the cluster
> is not empty (in terms of hosts) in order to prevent the Default cluster
> being changed on new deployments (not upgrades).

What about PowerPC clusters?

Comment 7 Nikolai Sednev 2020-07-06 13:16:12 UTC

Works for me on latest Software Version:4.4.1.7-0.3.el8ev.
ovirt-hosted-engine-ha-2.4.4-1.el8ev.noarch
ovirt-hosted-engine-setup-2.4.5-1.el8ev.noarch
Linux 4.18.0-193.12.1.el8_2.x86_64 #1 SMP Thu Jul 2 15:48:14 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.2 (Ootpa)

Reported issue no longer exists.

Comment 8 Sandro Bonazzola 2020-07-08 08:26:31 UTC

This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

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