Bug 1585990

Summary:	Empty cluster from upgraded 4.1 engine does not have Cluster CPU Type set
Product:	[oVirt] ovirt-engine	Reporter:	Lukas Svaty <lsvaty>
Component:	BLL.Infra	Assignee:	Eli Mesika <emesika>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	high	Docs Contact:
Priority:	urgent
Version:	4.2.4	CC:	bugs, dron, eedri, emesika, lleistne, lveyde, mperina, ratamir
Target Milestone:	ovirt-4.2.4	Keywords:	Automation, AutomationBlocker, Regression
Target Release:	---	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.4.5	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-26 08:39:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Svaty 2018-06-05 09:03:09 UTC

Description of problem:
When 4.1 engine with empty default datacenter is upgraded, Default datacenter keeps empty value for Cluster CPU Type which leads to fail of upgrade of the cluster to 4.2 version. During the upgrade process of 4.1 to 4.2 all empty Cluster CPU Types should be set to "Auto Detect"

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


How reproducible:


Steps to Reproduce:
1. Have 4.1 engine with empty cluster Default
2. Upgrade to 4.2 engine
3. Check Cluster CPU type of Default cluster (empty string)
4. Try to upgrade to 4.2 cluster compatibility version

Actual results:
08:44:21 2018-06-02 08:44:21,329 ERROR Result: FAILED
08:44:21 2018-06-02 08:44:21,330 ERROR  ERR: Failed to update element NOT as expected:
08:44:21 	Status: 400
08:44:21 	Reason: Bad Request
08:44:21 	Detail: [Cannot edit Cluster. The chosen CPU is not supported.]

Expected results:
Should succeed

Comment 1 Lukas Svaty 2018-06-05 09:19:21 UTC

This issue has WA in Automation -> 137646
For verification it would be sufficient to revert this patch.

Comment 3 Michal Skrivanek 2018-06-12 11:27:24 UTC

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

Comment 4 Martin Perina 2018-06-14 12:37:58 UTC

Moving back to POST as we have reverted the fix

Comment 5 Eyal Edri 2018-06-17 08:29:51 UTC

Does this means the original fix will be postponed now to 4.2.5?

Comment 6 Martin Perina 2018-06-18 12:11:00 UTC

Merged to 4.2

Comment 7 Lucie Leistnerova 2018-06-25 15:22:58 UTC

After upgrade engine 4.1 -> 4.2.4, CPU type is loaded in cluster's dialog automatically or is set by host upgrade from the engine.
And update of compatibility version was successful.

verified in ovirt-engine-4.2.4.5-0.1.el7_3.noarch

Comment 8 Sandro Bonazzola 2018-06-26 08:39:34 UTC

This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

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