mapping emc vnx cinder volume to instance

asked 2017-05-19 11:23:31 -0500

cbravo gravatar image

Hello there,

we are just starting a demo installation of Openstack. We managed to install a controller node and a compute node successfully and also installed the EMC VNX1 Cinder Driver.

The Controller and the compute are different nodes, and the EMC VNX1 driver was installed on the controller node. Everything works fine (lun created on the VNX, storage working fine, no errors) up to the moment where we want to attach the LUN to an instance.

Going through the error log, we noticed the following message:

Exception during message handling 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 155, in _process_incoming 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 222, in dispatch 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 192, in _do_dispatch 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server result = func(ctxt, new_args) 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 1517, in initialize_connection 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server raise exception.VolumeBackendAPIException(data=err_msg) 2017-05-19 11:37:29.910 24714 ERROR oslo_messaging.rpc.server VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Driver initialize connection failed **(error: Bad or unexpected response from the storage volume backend API: Host sczoscmp01 has no FC initiators).

sczoscmp01 is the compute node. This compute node was previously registered by hand to the VNX, an storage group created an a Boot LUN presented to the server (to install Ubuntu).

This is the config file for the cinder.conf

[vnx_array1] storage_vnx_pool_names = Pool_Openstack san_ip = * san_secondary_ip = san_login = san_password = naviseccli_path = /opt/Navisphere/bin/naviseccli default_timeout = 10 volume_driver = cinder.volume.drivers.dell_emc.vnx.driver.VNXDriver volume_driver=cinder.volume.drivers.emc.emc_cli_iscsi.EMCCLIFCDriver destroy_empty_storage_group = False volume_backend_name=backendA-Pool_Openstack_SAS initiator_auto_registration = True

maybe it has something to do with the compute previously registered at the Storage (FC) and added to a storage group?

The version I'm using is ocata with Ubuntu.

Thank you in advance.

Greetings,

C.

edit retag flag offensive close merge delete