Description of problem: I want to power off the host and not shut down the virtual machines, but instead save their state. Version-Release number of selected component (if applicable): iso installed from https://resources.ovirt.org/pub/ovirt-4.3/iso/ovirt-node-ng-installer/4.3.9-2020031917/el7/ovirt-node-ng-installer-4.3.9-2020031917.el7.iso How reproducible: Always Steps to Reproduce: 1. suspend all running vms that have disks on the storage domain 2. storage - storage domains - domain name - data center - maintenance 3. Actual results: When I attempt to do this on oVirt, I get the following message: "Error while executing action: Cannot deactivate Storage. VMs in a state other than "Down" were detected. -Please ensure all VMs associated with this Storage Domain are stopped and in the Down state first." Expected results: Allow placing the domain into maintenance mode, and instead of forbidding the action only warn that there are suspended vm's on it. Additional info: I can do this on a regular enterprise linux libvirt host but not on oVirt.
This request is not currently committed to 4.4.z, moving it to 4.5
The documentation text flag should only be set after 'doc text' field is provided. Please provide the documentation text and set the flag to '?' again.
Restoring from hibernation might fail after moving the memory volume (seems to be related to the fact the image format could change but not sure - I got an error about image magic) - thus, set it to high
high severity
Verified. Versions: ovirt-engine-4.5.0-743c0a787472.211.el8ev vdsm-4.50.0.7-1.el8ev Steps to Reproduce: 1. Suspend all running vms that have disks on the storage domain 2. storage - storage domains - domain name - data center - maintenance 3. Activate the SD again and run the VMS Results as expected: The SD was set to maintance mode when the VMs using it are suspended. There were no warnings or erros during the steps. After activating the SD back, the VMs run without any errors.
This bugzilla is included in oVirt 4.5.0 release, published on April 20th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.0 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.