Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1365087

Summary:	new VM disk is not marked as "bootable" by default
Product:	[oVirt] ovirt-engine	Reporter:	Tomas Jelinek <tjelinek>
Component:	Frontend.WebAdmin	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Kevin Alon Goldblatt <kgoldbla>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	acanan, amureini, bugs, sbonazzo, weiwang
Target Milestone:	ovirt-4.0.4	Flags:	amureini: ovirt-4.0.z? tjelinek: planning_ack? tnisan: devel_ack+ rule-engine: testing_ack+
Target Release:	4.0.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-26 12:36:41 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 Tomas Jelinek 2016-08-08 12:25:29 UTC

Description of problem:
in 3.6.x when going to VM->disks->new disk the "bootable" was marked as default.
The same for "new vm" -> in "instance images" section "create" -> the "bootable" was marked as default.

This is not the case for 4.0 and the bootable is not marked.

Comment 1 Tomas Jelinek 2016-09-01 11:25:34 UTC

*** Bug 1363587 has been marked as a duplicate of this bug. ***

Comment 2 Kevin Alon Goldblatt 2016-09-06 14:43:21 UTC

Tested with the following code:
----------------------------------------
rhevm-4.0.4-0.1.el7ev.noarch
vdsm-4.18.12-1.el7ev.x86_64

Tested with the following scenario:

Steps to Reproduce:
1. VM->disks->new disk the "bootable" IS NOW marked as default.
2. New Vm -> in "instance images" section "create" -> the "bootable" IS NOW marked as default.




Actual results:
The first disk is now marked as bootable by default

Expected results:



Moving to VERIFIED!