Bug 1566457

Summary:	Hot plug CPU is broken on 3.6 clusters after oVirt is upgraded to 4.2
Product:	[oVirt] ovirt-engine	Reporter:	Eli Mesika <emesika>
Component:	Database.Core	Assignee:	Eli Mesika <emesika>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, lsurette, lsvaty, mperina, rbalakri, Rhev-m-bugs, srevivo, ykaul
Target Milestone:	ovirt-4.2.3	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Target Release:	4.2.3.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.2.3.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-10 06:29:45 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 Eli Mesika 2018-04-12 11:04:36 UTC

Description of problem:

 When upgrading oVirt a 3.6 cluster losses its Hot plug cpu functionality since the config setting for that key has a wrong value 


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


How reproducible:

Always


Steps to Reproduce:
1.Have a 3.6 cluster in oVirt 3.6 with Hot plug CPU used 
2.Upgrade oVirt to 4.2 
3.Test  Hot plug CPU on the 3.6 cluster


Actual results:

3.6 cluster losses its Hot plug CPU functionality


Expected results:

3.6 cluster should support plug CPU functionality


Additional info:

The reason for this regression was a missing value in the config file for 3.6 and then he value was taken from the java code which was correct 
However, getting rid from config defaults in the java code and a wrong setting that was added to the config file broke the feature

Comment 1 Israel Pinto 2018-04-23 08:00:23 UTC

Verify with:
Engine version:4.2.3.2-0.1.el7

Hot plug CPU to VM in 3.6 cluster on 4.2 engine

Comment 2 Sandro Bonazzola 2018-05-10 06:29:45 UTC

This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

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