Bug 1545229

Summary:	Starting a VM with Direct LUN fail with libvirtError
Product:	[oVirt] vdsm	Reporter:	guy chen <guchen>
Component:	Core	Assignee:	Tal Nisan <tnisan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Avihai <aefrat>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.20.15	CC:	aefrat, bugs, ebenahar, tnisan
Target Milestone:	ovirt-4.2.2	Keywords:	AutomationBlocker, Regression
Target Release:	---	Flags:	rule-engine: ovirt-4.2+ rule-engine: blocker+
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-03-29 11:04:55 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:
Bug Depends On:	1468439
Bug Blocks:

Description guy chen 2018-02-14 12:37:32 UTC

Description of problem:

Starting a VM with Direct LUN attached to it fail with the following error :
libvirtError: unsupported configuration: Found duplicate drive address for disk with target name 'sda' controller='0' bus='0' target='0' unit='1'

Version-Release number of selected component (if applicable):
4.20.17

How reproducible:
Always

Steps to Reproduce:
1.Create a VM from a pool with 1 bootable disk
2.Attache to the VM a Direct LUN disk
3.Started the VM

Actual results:
VM fail with an error

Expected results:
VM starts

Additional info:
Without the Direct LUN attached the VM starts with no issue.
Logs will be attached

Comment 4 Raz Tamir 2018-02-14 13:17:38 UTC

Looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1529460
Or
https://bugzilla.redhat.com/show_bug.cgi?id=1536075

Comment 5 Red Hat Bugzilla Rules Engine 2018-02-18 11:58:39 UTC

This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 6 guy chen 2018-02-18 13:18:08 UTC

Additional information :

Engine version : 4.2.1.5-0.1
The error reproduce also on VM that are not a part of a pool

Comment 7 Avihai 2018-02-19 11:44:10 UTC

The issue did not reproduce at my Env with 4.2.2-0.1 .

Scenario:
1.Create a VM from a pool with 1 bootable disk (I used ISCSI disk)
2.Attach to the VM a Direct LUN disk
3.Started the VM

VM started without issues.

Comment 8 Avihai 2018-02-19 11:45:51 UTC

Correction for step 1 :
1.Create a VM with 1 bootable disk (I used ISCSI disk)

Comment 9 Tal Nisan 2018-02-26 15:56:21 UTC

OK, correct steps to reproduce after finally managing to do it:

1. Create a VM with two VirtIO-SCSI disks, one bootable
2. Run the VM (A crucial step)
3. Stop the VM
4. Add another VirtIO-SCSI disk with a name in lower alphabetical order (name it 'a', that should do
5. Attempt to run the VM again

Comment 10 Avihai 2018-03-06 09:16:26 UTC

rhv-4.2.2-4 release (containing ovirt-engine-4.2.2.2 ) is blocked, moving back to MODIFIED.

Please move back to 'ON QA' when next valid build is available.

Comment 11 Avihai 2018-03-06 14:45:16 UTC

rhv-4.2.2-4 release was release again about ~20H ago and now it's not blocked, moving back to ON_QA

Comment 12 Avihai 2018-03-07 09:18:39 UTC

Verified with Tal's scenario on 4.2.2.2-0.1

Comment 13 Sandro Bonazzola 2018-03-29 11:04:55 UTC

This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.