Bug 1317657

Summary: Next-run configuration is not applied after powering the VM off
Product: [oVirt] ovirt-engine Reporter: jniederm
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bugs, tjelinek
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-17 13:21:13 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:
Attachments:
Description Flags
engine log of powering off none

Description jniederm 2016-03-14 19:01:03 UTC 
Created attachment 1136271 [details]
engine log of powering off

Description of problem:
Changes in next-run configuration are lost (not applied) if vm is stopped using "power off" UI context menu option.

Version-Release number of selected component (if applicable):
4.0 master, commit acf5a3c

How reproducible:
100%

Steps to Reproduce:
1. Create and run VM in webadmin.
2. Decrease memory size of running VM (Edit VM > System > Memory Size)
3. (CHECK) New memory value is shown when Edit VM dialog is reopened
4. (CHECK) VM has orange circle delta icon
5. Power off VM
6. Check bottom panel, tab General for "Defined Memory" and "Defined Memory guaranteed".

Actual results:
Original unchanged values

Expected results:
Decreased values entered during edit
Comment 1 Tomas Jelinek 2016-03-17 13:21:13 UTC 

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