Bug 1136372

Summary:	Edit Instance Type doesn't work
Product:	[Retired] oVirt	Reporter:	meital avital <mavital>
Component:	ovirt-engine-core	Assignee:	Omer Frenkel <ofrenkel>
Status:	CLOSED CURRENTRELEASE	QA Contact:	meital avital <mavital>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.5	CC:	ecohen, gklein, iheim, lsvaty, michal.skrivanek, nsimsolo, ofrenkel, rbalakri, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	ovirt-3.5.0_rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:37:00 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 meital avital 2014-09-02 12:56:20 UTC

Description of problem:
Edit Instance Type doesn't work

Version-Release number of selected component (if applicable):
ovirt-3.5.0_rc1.1

How reproducible:
100%

Steps to Reproduce:
1.Create new instance type
2.Create a vm with this instance type
3.Run the VM
4.Edit the instance type
5.Stop the VM
6.Start the VM


Actual results:
The update/edit not reflected to the vm

Expected results:
The VM should start with the new parameters 

Additional info:
happened also for edit original instance type, not just for new instance type

Comment 1 Lukas Svaty 2014-09-16 12:59:49 UTC

verified in vt3

Comment 2 meital avital 2014-09-23 12:37:27 UTC

Edit Instance type to lower CPU when the VM is running, the edit not reflected to the VM cause :
Failed to hot set number of CPUS to VM il. Underlying error message: Hot un-plugging a CPU is not supported for cluster version 3.5 and architecture x86_64.

The parameters not reflected also when the VM stop and start again.

Comment 3 Omer Frenkel 2014-09-23 12:40:17 UTC

i guess using hot plug on the vms when updating instance type is not a good approach, as if it fails/disabled, the value is not saved for next run, but rolled back.

Comment 4 Michal Skrivanek 2014-09-26 12:14:18 UTC

worth getting in 3.5 still, but shouldn't really block if it's the last thing preventing GA

Comment 5 Sandro Bonazzola 2014-10-17 12:37:00 UTC

oVirt 3.5 has been released and should include the fix for this issue.

Comment 6 Nisim Simsolo 2014-12-30 09:29:26 UTC

Verified on downstream, fix is valid (vt13.1).