Bug 1001030

Summary: [rhevm] Backend - VM Bootable vDisk is changed when adding the third vDisk
Product: Red Hat Enterprise Virtualization Manager Reporter: David Botzer <dbotzer>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED NOTABUG QA Contact: Aharon Canan <acanan>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, iheim, lpeer, michal.skrivanek, pstehlik, Rhev-m-bugs, scohen, yeylon
Target Milestone: ---Keywords: Triaged
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-01 13:39:35 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:
Attachments:
Description Flags
pic
none
engine
none
vdsm none

Description David Botzer 2013-08-26 11:14:04 UTC 
Created attachment 790429 [details]
pic

Description of problem:
[rhevm] Backend - VM Bootable vDisk is changed when adding the third vDisk

Version-Release number of selected component (if applicable):
3.3/is11

How reproducible:
always

Steps to Reproduce:
1.create vm with 1 disk
2.add 2 vDisk
3.Start VM

Actual results:
VM cannot boot, since its bootable disk was changed

Expected results:
Bootable vDisk should change when adding additional disks

Additional info:
Workaround - 
Stop the VM and edit the vDisk it to be bootable
Comment 1 David Botzer 2013-08-26 11:15:08 UTC 
Created attachment 790430 [details]
engine
Comment 2 David Botzer 2013-08-26 11:15:30 UTC 
Created attachment 790431 [details]
vdsm
Comment 3 Itamar Heim 2013-08-27 07:20:19 UTC 
david - how is this infra? its either storage or virt
setting storage since they are tackling disk boot order in another bug.
Comment 4 David Botzer 2013-09-01 13:39:35 UTC 
David:
With Blank VM its not reproducible
The first & only disk in the template is not marked as Bootable, but contains the OS and vm starts ok,
--------------------
I have a template with 1 disk.
A VM created from template (Thin/Clone) has 1 disk which is marked as not-bootable therefore each new disk suggested to be bootable (check box is "is bootable" is enabled)