Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 929091

Summary: Can not connect to FC storage with rhevm-sf12(only occurs in 3.2 cluster)
Product: Red Hat Enterprise Virtualization Manager Reporter: haiyang,dong <hadong>
Component: ovirt-engine-webadmin-portalAssignee: Ayal Baron <abaron>
Status: CLOSED WORKSFORME QA Contact: Haim <hateya>
Severity: high Docs Contact:
Priority: medium    
Version: 3.2.0CC: acathrow, amureini, chchen, cshao, dyasny, ecohen, gouyang, hadong, hateya, iheim, leiwang, Rhev-m-bugs, ycui, yeylon, ykaul
Target Milestone: ---   
Target Release: 3.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-01 02:44:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
attached Screenshot for the lun in free is grayed out.png none

Description haiyang,dong 2013-03-29 08:53:12 UTC 
Created attachment 717974 [details]
attached Screenshot for the lun in free is grayed out.png

Description of problem:
Check this screenshot, the lun in free is grayed out. so this free device couldn't be selected to use it. And the lun in
used isn't grayed out, it can be selected to use.

Version-Release number of selected component (if applicable):
rhev-hypervisor-advanced-6.4-20130328.0.el6ev
vdsm-4.10.2-13.0.el6ev.x86_64
Red Hat Enterprise Virtualization Manager Version: 3.2.0-10.17.master.el6ev

How reproducible:
100%

Steps to Reproduce:
1. install RHEVH on a machine.
2. Register to RHEVM-sf12(3.2 cluster).
3. Create a FC storage data domain.
  
Actual results:

Expected results:
the lun in free isn't grayed out. so this free device can be selected to use it. And the lun in
used is grayed out, so it can't be selected to use.

Additional info:
Comment 1 Haim 2013-03-29 20:10:32 UTC 
we need more logs in order to understand the problem.

please attach engine, vdsm and messages logs.

also:

- lsblk
- multipath -ll
- pvs -a