Created attachment 953833 [details]
engine.log and /var/log/ from host

Description of problem:
After installing a guest from CD-ROM using an ISO from Run-once, the VM gets rebooted. When it boots, the boot order remains as it was configured in Run-once and not as it is configured in the VM persistemt configuration. The VM boots from the CD-ROM again and it has to be powered-off/shut-down and start again in order to boot from the configured device (hard-disk).


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

How reproducible:
rhev 3.5 vt8

Steps to Reproduce:
Have an active ISO domain in the DC
1. Create a VM and start it from Run-once. Change the boot order so the VM will boot from CD-ROM. Pick an ISO from the ISO domain
2. Install OS. Once OS installation is done, the VM will be rebooted automatically or the guest will ask the user to reboot it


Actual results:

VM enter to 'rebooting' state:

2014-11-04 17:29:53,506 INFO  [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-31) VM vm-2 2a16d463-4ac5-446d-abb2-c7c1605cc8f3 moved from U
p --> RebootInProgress

And then to Up:

2014-11-04 17:30:54,344 INFO  [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-12) VM vm-2 2a16d463-4ac5-446d-abb2-c7c1605cc8f3 moved from R
ebootInProgress --> Up


VM is still in 'Run-once' mode. It boots from CD-ROM once again instead of booting from the defined device configured in the persistent VM configuration. 

VM boot sequmce after the VM started:
# select vm_name,boot_sequence from vms;

 vm_name | boot_sequence 
---------+---------------
 vm-2    |             5


After that, I powered-off the VM and started it. Boot sequmce after the VM was started:
 
 vm_name | boot_sequence 
---------+---------------
 vm-2    |             0



2014-11-04 22:53:05,290 INFO  [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-39) [10bdb7b4] VM vm-2 2a16d463-4ac5-446d-abb2-c7c1605cc8f3 moved from PoweringUp --> Up


Now the boot sequnce changed to the persistent configuration.

Expected results:
VM shouldn't start in Run-once after the installation has completed and it was rebooted.


Additional info: engine.log and /var/log/ from host