Bug 1001030 - [rhevm] Backend - VM Bootable vDisk is changed when adding the third vDisk
Summary: [rhevm] Backend - VM Bootable vDisk is changed when adding the third vDisk
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Nobody
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-26 11:14 UTC by David Botzer
Modified: 2016-02-10 18:05 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-01 13:39:35 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
pic (92.81 KB, image/png)
2013-08-26 11:14 UTC, David Botzer 		no flags Details
engine (179.26 KB, application/x-gzip)
2013-08-26 11:15 UTC, David Botzer 		no flags Details
vdsm (836.56 KB, application/x-gzip)
2013-08-26 11:15 UTC, David Botzer 		no flags Details
View All

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)
Note You need to log in before you can comment on or make changes to this bug.