Description of problem:
Read VM next_run, via REST, show 'console', and 'boot sequence' are not updated
with the new values, set in VM via UI Edit running VM.
They have the value of current VM configuration.
Version-Release number of selected component (if applicable):
VM current run should show all "NEXT BOOT" parameters.
The following parameters were tested as well, and their values were found CORRECT in the next_run:
memory, guaranteed memory, monitors, usb policy, cdrom change
the issue is that rest api has a feature to show 'dynamic' values (that contain the current run info) if it exists, so it overrides the next-run values.
Tested on rhevm 3.6.0-17.
Edit a running VM with these changes, that will apply only after next VM boot:
- console changed from spice to vnc
- boot sequence changed from first hard disk to network first, and then CD rom.
Still the next_run output show the VM current_run, instead of next_run, as expected.
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.
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset.
Please set the correct milestone or add the flag.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Please note that the ;next_run still does not work for the legacy <display> and it will not be fixed since the <display> does not support the option to have more than one displays at once. To find the correct next_run configuration you need to check the /graphicsconsoles subresouce.
Engine Version: 18.104.22.168-0.1.el7ev
OS Version:RHEL - 7.2 - 9.el7_2.1
OS Description:Kernel Version:3.10.0 - 327.22.2.el7.x86_64
KVM Version:2.3.0 - 31.el7_2.16
SPICE Version:0.12.4 - 15.el7_2.1
1. Create VM and run it
2. Edit running VM with the following parameters:
monitors, boot sequence, guaranteed memory,
Migration: 'Do not allow migration'
3. Check the UI reports the next run updates
4. Check with REST API the next_nun configuration as expected
in https://<engine ip>:443/ovirt-engine/api/vms/<vm_id>;next_run
and the flag is true:
5. Display check compare current to next run:
6. Reboot VM and check that parameters updated