Bug 1430451

Summary:	Make max memory to follow memory only when VM is not UP
Product:	[oVirt] ovirt-engine	Reporter:	jniederm
Component:	Frontend.WebAdmin	Assignee:	jniederm
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	future	CC:	bugs, lveyde, michal.skrivanek
Target Milestone:	ovirt-4.1.2	Flags:	rule-engine: ovirt-4.1+
Target Release:	4.1.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-23 08:20:46 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 jniederm 2017-03-08 15:52:10 UTC

Description of problem:
Currently when memory is changed in edit vm dialog, then max memory is always updated. Intended state is to max memory following value of memory only if the VM is it state other than UP.

Comment 1 Israel Pinto 2017-05-04 08:08:21 UTC

Verify with: 
RHVM Version: 4.1.2-0.1.el7

Steps:
1.[Running VM]
Start VM (vm is in UP status) 
Update VM memory, check that max memory did not updated.
1.[Non running VM]
Update VM memory, check that max memory updated to memory*4.

Results:
All cases pass