Bug 1077568 - Cannot change template's guaranteed memory
Summary: Cannot change template's guaranteed memory
Keywords:
Status: CLOSED DUPLICATE of bug 731359
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6.0
Assignee: Doron Fediuck
QA Contact: Pavel Stehlik
URL:
Whiteboard: sla
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-18 09:16 UTC by Arik
Modified: 2016-02-10 19:41 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-25 10:28:52 UTC
oVirt Team: SLA
Embargoed:


Attachments (Terms of Use)

Description Arik 2014-03-18 09:16:58 UTC
Description of problem:
Now that we prevent the guaranteed memory from being bigger than the memory size (bz 1045131), we should allow to change the guaranteed memory for templates as well.

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

How reproducible:
100%

Steps to Reproduce:
1. Create VM with 4 gb of RAM (the guaranteed memory is 4 gb by-default)
2. Create a template which is based on the VM above
3. Using edit-template dialog, try to decrease the memory size of the template

Actual results:
The operation fails because the guaranteed memory will be bigger than the memory size

Expected results:
The user should be able to change the guaranteed memory or we could change the guaranteed memory to the new value of the memory size, to make it possible to decrease the memory size of the template

Additional info:

Comment 1 Sandro Bonazzola 2014-05-08 13:55:49 UTC
This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.

Comment 2 Martin Sivák 2014-07-23 08:54:33 UTC
Setting the guaranteed memory to the lower memory size when editing template sounds like a good plan.

Comment 4 Doron Fediuck 2015-08-25 10:28:52 UTC

*** This bug has been marked as a duplicate of bug 731359 ***


Note You need to log in before you can comment on or make changes to this bug.