Bug 1539778 - Under Instance Images: Selected LUN is unmarked while editing an added direct LUN in new VM prompt
Summary: Under Instance Images: Selected LUN is unmarked while editing an added direct...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 4.2.1.2
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ovirt-4.2.2
: ---
Assignee: shani
QA Contact: Yosi Ben Shimon
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-29 15:23 UTC by Yosi Ben Shimon
Modified: 2018-03-29 11:14 UTC (History)
6 users (show)

Fixed In Version: ovirt-engine-4.2.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-29 11:14:45 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)
LUN video (1.09 MB, image/gif)
2018-01-29 15:23 UTC, Yosi Ben Shimon 		no flags Details
Seems it happen also for 4.1 (1.72 MB, image/gif)
2018-01-30 11:10 UTC, shani 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 87162 0 master MERGED webadmin: Mark LUN as selected when editing a disk 2018-02-06 14:05:54 UTC

Description Yosi Ben Shimon 2018-01-29 15:23:09 UTC 
Created attachment 1387853 [details]
LUN video

Description of problem:
While in creation process of new VM and after adding a new direct LUN.
If i click on 'edit' button for that LUN, the previously selected LUN is unmarked. 
See attached video capture.

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


How reproducible:
always.

Steps to Reproduce:
1. Click on the 'New' button for new VM
2. Click on the 'Create' button under 'Instance Images' for new disk.
3. Select the 'Direct LUN' on top.
4. Set value for 'Alias'.
5. Select an arbitrary LUN and click 'OK'.
6. after the 'new Virtual Disk' window is closed, click on the 'Edit' button just next to the newly created disk.
7. Expend the target by clicking on the '+' to the left to see the LUNs.


Actual results:
No LUN is marked.

Expected results:
The previously selected LUN is marked.

Additional info:
Comment 1 Allon Mureinik 2018-01-29 19:07:37 UTC 
I'm pretty sure this is a regression.
Yosi, Shani, feel free to keep me honest here.
Comment 2 Red Hat Bugzilla Rules Engine 2018-01-29 19:07:40 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 3 shani 2018-01-30 11:10:05 UTC 
Created attachment 1388299 [details]
Seems it happen also for 4.1

It seems to happen also for ovirt-engine-4.1, so I guess it's not a regression.
(I've attached a gif for it)
Comment 4 Allon Mureinik 2018-01-31 08:12:47 UTC 
Removing the Regression keyword based on that analysis.
Thanks Shani.
Comment 5 Allon Mureinik 2018-02-07 10:08:06 UTC 
Shani - the attached patch is merged.
Should the bug move to MODIFIED, or are we waiting for another patch?
Comment 6 Yosi Ben Shimon 2018-02-18 10:35:59 UTC 
Tested using:
ovirt-engine-4.2.2-0.1.el7.noarch

Expected result:
The right LUN is selected.
The right result happens also after VM is created and adding another LUN. Shows the right LUN ID.

Moving to VERIFIED
Comment 7 Yosi Ben Shimon 2018-02-18 10:41:04 UTC 
Fix comment #6:
* Actual result:

Wrote by mistake.
Comment 8 Sandro Bonazzola 2018-03-29 11:14:45 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.
Note You need to log in before you can comment on or make changes to this bug.