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

Bug 1368954

Summary: CDA log of attaching second boot disk is wrong
Product: [oVirt] ovirt-engine Reporter: Raz Tamir <ratamir>
Component: BLL.StorageAssignee: Tal Nisan <tnisan>
Status: CLOSED CURRENTRELEASE QA Contact: Kevin Alon Goldblatt <kgoldbla>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.0.2.6CC: amureini, bugs, istein
Target Milestone: ovirt-4.0.4Keywords: Automation
Target Release: 4.0.4Flags: tnisan: ovirt-4.0.z?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+
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:39:59 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 Raz Tamir 2016-08-22 08:46:10 UTC
Description of problem:
When trying to attach a second bootable disk to VM, the CDA message in engine.log is wrong:
"Cannot attach Virtual Disk. Disk ${DiskName} in VM ${VmName} is already marked as boot., vmname, vm type 22113446, diskname, vm type 22113446 disk1"


Version-Release number of selected component (if applicable):
ovirt-engine-4.0.2.6-0.1.el7ev.noarch

How reproducible:
100&

Steps to Reproduce:
1. Attach second boot disk to VM with already attached disk as boot
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Raz Tamir 2016-08-23 13:38:58 UTC
Tal,
Should I open a new bug on wrong log message when moving template disk?
the log message:
Status: 400
Reason: Bad Request
Detail: [Cannot move Virtual Disk. The following disk(s) are not attached to any VM: ${diskAliases}.]

Comment 2 Kevin Alon Goldblatt 2016-09-07 15:32:44 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. Attach second boot disk to VM with already attached disk as boot >>>>
The following error is generated:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fault>
    <reason>Operation Failed</reason>
    <detail>[Cannot add Virtual Disk. Disk vm44_Disk1 in VM vm44 is already marked as boot.]</detail>
</fault>


Actual results:
The correct error is reported indicating that the vm already has a bootable disk

Expected results:



Moving to VERIFIED!

Comment 3 Juan Hernández 2016-09-08 08:13:37 UTC
*** Bug 1373880 has been marked as a duplicate of this bug. ***