Bug 1251721 – Deactivating a VM's sole bootable disk while VM is running is valid.

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.

Status:	CLOSED NOTABUG

Aliases:	None

Product:	oVirt
Classification:	Community
Component:	ovirt-engine-core (Show other bugs)
Sub Component:
Version:	3.6
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	m1
Target Release:	3.6.0
Assigned To:	Allon Mureinik
QA Contact:	Pavel Stehlik
Docs Contact:

URL:
Whiteboard:	storage
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-08-09 03:51 EDT by Amit Aviram
Modified:	2016-03-10 01:13 EST (History)
CC List:	7 users (show)

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: 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:
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 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.

closing.

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