Created attachment 1359702 [details] More than one LUN seems to be selected (one for each target) Description of problem: When creating a new direct LUN disk for a new VM using Targets > LUNs table, there is an option for choosing more than one LUN by choosing one of each target. Version-Release number of selected component (if applicable): 108f58769dd5cbe36006c38aa2998ec0fe2ad208 How reproducible: 100% Steps to Reproduce: 1. press the 'new' button on VMs screen 2. under 'Instance Images' press 'create' for a new disk and choose the direct lun tab 3. on Targets > LUNs table, choose a lun from each target available Actual results: All selected luns appear so be selected (buttons pressed on) Expected results: Only one LUN (the last one selected) should be press on Additional info: -
Created attachment 1387800 [details] image1
Created attachment 1387802 [details] image2
Created attachment 1387804 [details] video3
According to the "steps to reproduce" in the description, this bug is not verified because the bug is still exists. See attached screen shot (image1.png) Tested using: ovirt-engine-4.2.1.3-0.1.el7.noarch Note that while verifying this bug, i came across the next bug: I can select more then one LUN in the same target. See attached screen shot (image2.png) and video capture (video3.gif) Steps to reproduce: 1. press the 'new' button on VMs screen 2. under 'Instance Images' press 'create' for a new disk and choose the direct lun tab 3. on Targets > LUNs table, choose a lun from each target available 4. switch vertical tab to 'LUNs > Targets' 5. switch back to 'Targets > LUNs' tab 6. expend any target (one of the LUNs is already selected) 7. select another LUN in that target Actual results: Two LUNs can be selected under the same target.
A fix has been uploaded.
Tested using: ovirt-engine-4.2.2-0.1.el7.noarch Actual result: Only one LUN can be selected at a time. Moving to VERIFIED
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.