Hide Forgot
Description of problem: Due to changes in the validator that is used before running VM (patch: I772377045d5c6d694e00006c9b12e210c52ab353) we always allow to resume paused VMs without checking the status of the host they are going to be resumed on. It leads to situation where paused VM can be resume on non-operational host, which we used to block before 3.3. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. run VM in pause mode 2. block the connectivity between the host and the storage 3. wait for the host to become non-operational (wait 5 minutes) 4. run the VM Actual results: the VM is resumed Expected results: the VM shouldn't be resumed with a proper error message Additional info:
is this worth oVirt 3.3.2?
(In reply to Michal Skrivanek from comment #1) > is this worth oVirt 3.3.2? I don't think so. it happens in rare negative flows.
oVirt 3.4.0 alpha has been released including the fix for this issue.
Verified in ovirt-engine-3.4.0-0.7.beta2.el6.noarch. Followed reproducer in comment 0 for verification. Results: Error dialog is shown when attempting to resume the paused VM on an host that is not Up, e.g., Non Operational, Initializing, etc. -~- Error while executing action: paused-vm: Cannot run VM. Operation can be performed only when Host status is Up. -~-
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released