Bug 1251721 - Deactivating a VM's sole bootable disk while VM is running is valid.
Deactivating a VM's sole bootable disk while VM is running is valid.
Product: oVirt
Classification: Community
Component: ovirt-engine-core (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: m1
: 3.6.0
Assigned To: Allon Mureinik
Pavel Stehlik
Depends On:
  Show dependency treegraph
Reported: 2015-08-09 03:51 EDT by Amit Aviram
Modified: 2016-03-10 01:13 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-08-09 04:39:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Amit Aviram 2015-08-09 03:51:13 EDT
Description of problem:
Deactivating a VM's sole bootable disk while the VM is running is valid, while activating VMs with no bootable disks is not supported. This causes an inconsistent behavior in the system.

How reproducible:

Steps to Reproduce:
1. Add a VM.
2. Add a bootable disk.
3. Run the VM.
4. Deactivate the disk.

Actual results:
Deactivation succeeds.

Expected results:
Deactivation should fail, as this is the sole bootable device.
Comment 1 Allon Mureinik 2015-08-09 04:39:23 EDT
Once a VM is up it no longer really needs a bootable device. I'd much rather keep consistency between cold (un)plugging and hot un(plugging) than running a VM and editing its state while it's up.


Note You need to log in before you can comment on or make changes to this bug.