[rhev 3] add new domain fails: Could not retrieve LUNs

Latest response

Hi all,

I'm trying to configure a FCP storage domain on RHEV 3.

I try to add a new domain from the console, but it can't find any LUNs: "Could not retrieve LUNs, please check your storage"

 

 

Here is the output from /var/log/rhevm/rhevm.log:

 ------------------------------------

2007-06-29 21:50:07,811 WARN  [org.ovirt.engine.core.bll.GetConfigurationValueQuery] (http-0.0.0.0-8443-1) calling GetConfigurationValueQuery with null version, using default general for version
2007-06-29 21:50:07,911 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (http-0.0.0.0-8443-1) START, GetDeviceListVDSCommand(vdsId = 7e077f4c-25d8-11dc-bbcb-001cc4c2469a, storageType=FCP), log id: 60bdafe6
2007-06-29 21:50:08,726 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-1) Failed in GetDeviceListVDS method
2007-06-29 21:50:08,727 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-1) Error code BlockDeviceActionError and error message VDSGenericException: VDSErrorException: Failed to GetDeviceListVDS, error = Error block device action: ()
2007-06-29 21:50:08,727 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-1) Command org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand return value

Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.LUNListReturnForXmlRpc
lunList                       Null
mStatus                       Class Name: org.ovirt.engine.core.vdsbroker.vdsbroker.StatusForXmlRpc
mCode                         600
mMessage                      Error block device action: ()

 

2007-06-29 21:50:08,727 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.BrokerCommandBase] (http-0.0.0.0-8443-1) Vds: pittor06vhxd020
2007-06-29 21:50:08,727 ERROR [org.ovirt.engine.core.vdsbroker.VDSCommandBase] (http-0.0.0.0-8443-1) Command GetDeviceListVDS execution failed. Exception: VDSErrorException: VDSGenericException: VDSErrorException: Failed to GetDeviceListVDS, error = Error block device action: ()
2007-06-29 21:50:08,727 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (http-0.0.0.0-8443-1) FINISH, GetDeviceListVDSCommand, log id: 60bdafe6
2007-06-29 21:50:08,727 ERROR [org.ovirt.engine.core.bll.storage.GetDeviceListQuery] (http-0.0.0.0-8443-1) Query GetDeviceListQuery failed. Exception message is VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to GetDeviceListVDS, error = Error block device action: ()

----------------------------------------------

 

First question: do LUNs have to be visible from RHEV-H or RHEV-M?

Currently they are visible only from the hypervisor.

----------------------------------------

[root@pittor06vhxd020 log]# multipath -ll
3600601601cde1d0066b2fb054dece111 dm-2 DGC,RAID 5
size=650G features='1 queue_if_no_path' hwhandler='1 emc' wp=rw
|-+- policy='round-robin 0' prio=1 status=active
| |- 2:0:0:0 sda        8:0    active ready running
| |- 2:0:1:0 sdd        8:48   active ready running
| |- 3:0:0:0 sde        8:64   active ready running
| `- 3:0:1:0 sdf        8:80   active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
  |- 2:0:2:0 sdb        8:16   active ready running
  |- 2:0:3:0 sdc        8:32   active ready running
  |- 3:0:2:0 sdg        8:96   active ready running
  `- 3:0:3:0 sdh        8:112  active ready running
3600508b1001035333920202020200005 dm-0 HP,LOGICAL VOLUME
size=205G features='1 queue_if_no_path' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
  `- 0:0:1:0 cciss!c0d1 104:16 active ready running
------------------------------------------------------

 

Our SAN device is Clariion AX150. Is it compatible with rhev 3?

 

Thank you very much for any hints.

 

AS

Responses

Hi,

 

OK, lets answer this step by step.

1. RHEV can use Clariion (we actually have a few in our testing labs)

2. RHEV-M does not need to access the SAN, it only sends a call to the hypervisors to do so

3. RHEV requires a blank, raw LUN, so if there is a filesystem or an LVM structure already existing on the LUN you are presenting, RHEV will ignore it, so as not to delete important data by accident

 

 

So here's the action plan:

1. make sure the LUN is blank, if it is not, just dd if=/dev/zero of=/dev/mapper/3600601601cde1d0066b2fb054dece111 for a few seconds to wipe the partition tables

2. try to add the LUN again

 

If this fails, please post the output of `vdsClient -s 0 getDeviceList ` on the hypervisor. If there is nothing there, this might need to become a support ticket with a sosreport or log collector output attached