+++ This bug was initially created as a clone of Bug #1343934 +++
Description of problem:
When changing the CPU profile on a running VM you get notified that the profile only takes effect after a VM restart. After klicking OK the VM gets the symbol assign which indicates that there is a configuration update which did not jet take effect.
When checking the VM config again you see that the CPU profile is still the old one. Also a VM restart keeps the old profile.
Doing the changes on a VM which is down work as expected.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Create a second CPU profile
2. Create and start a VM
3. Edit the VM and set the new CPU profile
4. Restart the VM to make the new CPU profile effective
5. The VM still has the old CPU profile
Actual results:
There is way to edit the CPU profile on a running VM. The change just gets lost.
It is not live updated and it is not persisted for later VM starts.
Expected results:
The CPU profile should be live updated on the running VM and saved to the database.
Additional info:
--- Additional comment from Red Hat Bugzilla Rules Engine on 2016-06-09 03:32:38 EDT ---
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
--- Additional comment from Yaniv Dary on 2016-07-21 08:58:14 EDT ---
Should this be modified?
--- Additional comment from Tomas Jelinek on 2016-07-29 03:42:00 EDT ---
I think this causes this regression: https://bugzilla.redhat.com/show_bug.cgi?id=1361366
Verified on Red Hat Enterprise Virtualization Manager Version: 3.6.9-0.1.el6
1) Create two cluster profiles with CPU QoS 10 and 20
2) Attach CPU profile with QoS 10 to VM
3) Start VM
4) Change VM CPU profile with QoS 20
5) power off VM
6) Start vm -> check the the CPU profile of the VM is the new one
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2016-1929.html