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
Looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1529460 Or https://bugzilla.redhat.com/show_bug.cgi?id=1536075
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.
Additional information : Engine version : 4.2.1.5-0.1 The error reproduce also on VM that are not a part of a pool
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.
Correction for step 1 : 1.Create a VM with 1 bootable disk (I used ISCSI disk)
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
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.
rhv-4.2.2-4 release was release again about ~20H ago and now it's not blocked, moving back to ON_QA
Verified with Tal's scenario on 4.2.2.2-0.1
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.