Bug 1430451 - Make max memory to follow memory only when VM is not UP
Summary: Make max memory to follow memory only when VM is not UP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: future
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.2
: 4.1.2
Assignee: jniederm
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-08 15:52 UTC by jniederm
Modified: 2017-05-23 08:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-23 08:20:46 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1388245 0 unspecified CLOSED [RFE] Configurable maximum memory size 2021-02-22 00:41:40 UTC
oVirt gerrit 74089 0 master MERGED webadmin: Max memory doesn't follow memory if VM is UP 2020-03-12 11:38:13 UTC
oVirt gerrit 74146 0 ovirt-engine-4.1 MERGED webadmin: Max memory doesn't follow memory if VM is UP 2020-03-12 11:38:13 UTC

Internal Links: 1388245

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
Note You need to log in before you can comment on or make changes to this bug.