Created attachment 588109 [details] log Description of problem: we are blocked from adding a second disk to vm after attaching a floating disk with error: Cannot add Virtual Machine Disk. The chosen disk drive letter is already in use, please select a free one. this is both for automated disk alias selection and when manually chaning the disk alais. I tested the below: 1. vm with no disk -> attach a disk -> try to create a new disk = fail 2. vm with existing disk -> attach a disk -> try to create a new disk = fail 3. vm with existing disk -> attach a disk -> try to attach a second disk = fail backend can_do is: 2012-05-28 17:21:47,593 WARN [org.ovirt.engine.core.bll.AddDiskCommand] (ajp--0.0.0.0-8009-2) [3daca1df] CanDoAction of action AddDisk failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__VM_DISK,ACTION_TYPE_FAILED_DISK_LETTER_ALREADY_IN_USE I tested both for disks Version-Release number of selected component (if applicable): si4 How reproducible: 100% Steps to Reproduce: 1. create a vm with no disks 2. attach a disk that was created as floating disk 3. try to add a second disk to the vm Actual results: we are blocked with can_do_action from backend about disk name Expected results: we should be able to create/attach another disk Additional info:full log
The following commit will solve a bug: http://gerrit.ovirt.org/#change,4984 From now, there are no internal drive mapping at the system
*** Bug 819908 has been marked as a duplicate of this bug. ***
verified on si6