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
This issue has WA in Automation -> 137646 For verification it would be sufficient to revert this patch.
*** Bug 1554377 has been marked as a duplicate of this bug. ***
Moving back to POST as we have reverted the fix
Does this means the original fix will be postponed now to 4.2.5?
Merged to 4.2
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
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.