Bug 1330483

Summary: [z-stream clone - 3.6.6] Storage domain ownership of LUN not displayed.
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-engineAssignee: Fred Rolland <frolland>
Status: CLOSED ERRATA QA Contact: Elad <ebenahar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.6.5CC: acanan, amureini, ebenahar, gklein, lsurette, pdwyer, ratamir, rbalakri, Rhev-m-bugs, sbonazzo, srevivo, tnisan, ykaul, ylavi
Target Milestone: ovirt-3.6.6Keywords: Regression, ZStream
Target Release: 3.6.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1329906 Environment:
Last Closed: 2016-05-25 12:08:30 UTC Type: ---
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: 1329906    
Bug Blocks:    
Attachments:
Description Flags
Screen capture none

Comment 3 Elad 2016-05-02 09:13:57 UTC
Created attachment 1152895 [details]
Screen capture

Hovering over a LUN that is used by FC domain doesn't open a tool tip with the reason why it's greyed out.
Attaching a capture of my screen while hovering over such LUN in create new FC domain prompt.

rhevm-3.6.6-0.1.el6.noarch
rhevm-webadmin-portal-3.6.6-0.1.el6.noarch

Moving to ASSIGNED

Comment 4 Tal Nisan 2016-05-03 08:48:40 UTC
Don't know why this was moved to ON_QA, I've checked the relevant build and this patches was not included in it, moving back to MODIFIED so it will be tested against the next version.

Comment 5 Elad 2016-05-08 12:44:11 UTC
While hovering over a LUN which is used as part of a FC/iSCSI domain, a tool-tip is shown with the reason why this LUN is greyed-out.


Verified using
rhevm-3.6.6.2-0.1.el6.noarch
rhevm-webadmin-portal-3.6.6.2-0.1.el6.noarch
vdsm-4.17.28-0.el7ev.noarch

Comment 7 errata-xmlrpc 2016-05-25 12:08:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://rhn.redhat.com/errata/RHBA-2016-1119.html