Bug 1251721 - Deactivating a VM's sole bootable disk while VM is running is valid.
Summary: Deactivating a VM's sole bootable disk while VM is running is valid.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: m1
: 3.6.0
Assignee: Allon Mureinik
QA Contact: Pavel Stehlik
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-09 07:51 UTC by Amit Aviram
Modified: 2016-03-10 06:13 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-09 08:39:23 UTC
oVirt Team: Storage
Embargoed:

Attachments (Terms of Use)

Description Amit Aviram 2015-08-09 07:51:13 UTC 
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:
100%


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 08:39:23 UTC 
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.

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