Bug 1251721

Summary:	Deactivating a VM's sole bootable disk while VM is running is valid.
Product:	[Retired] oVirt	Reporter:	Amit Aviram <aaviram>
Component:	ovirt-engine-core	Assignee:	Allon Mureinik <amureini>
Status:	CLOSED NOTABUG	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6	CC:	amureini, bugs, ecohen, gklein, lsurette, rbalakri, yeylon
Target Milestone:	m1
Target Release:	3.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-09 08:39:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.