Description of problem: Reboot a powering up vm with next-run configuration, the vm changes to reboot in process state first, then goes to down status, it doesn't start again. The down vm can be started manually, but when powering off the vm after it's up, the vm will enter restart process but not be powered off. Version-Release number of selected component (if applicable): ovirt-engine-4.4.4.6-0.1.el8ev.noarch How reproducible: 100% Steps to Reproduce: 1. Start a VM that is not installed with qemu-guest-agent (so it will take the VM 60 sec to reach UP state) 2. Right after starting the VM, edit the VM to produce next-run configuration (e.g., add/remove ballooning) 3. Before the VM reaches UP state, reboot the VM Actual results: 1. The vm becomes down, doesn't start again. Expected results: 1. The vm could be restarted. Additional info:
Verified with: ovirt-engine-4.5.2.1-0.1.el8ev.noarch Steps: The same steps as in the bug description. Results: The powering up VM with next-run configuration could be restarted successfully, the next-run configuration takes effect after reboot.
This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.