Answer by jgriffith for I have a block storage configured using Cinder (on Juno). A new volume was created and its state shows as "available". I have a nova instance (a test Cirros instance) configured. I want to attach this existing cinder volume to the nova instance. After trying nova volume-attach "instance ID" "volume ID" "/dev/vdb" OR nova volume-attach "instance ID" "volume ID" "auto" , the state of the volume changes from "attaching" and then back to "available" and the "attached to" field is blank. Nothing on 'fdisk -l' on the cirros instance. This cirros is running on a KVM (on a virtual machine) - and this virtual machine is running on VMware Esxi. So, this is sort of a nested virtualization. OUTPUT of lvs and vgs on RHEL65. [root@rhel65-03 nova]# lvs LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert lv_root vg_rhel6501 -wi-ao---- 44.65g lv_swap vg_rhel6501 -wi-ao---- 4.86g [root@rhel65-03 nova]# vgs VG #PV #LV #SN Attr VSize VFree cinder-volumes 1 0 0 wz--n- 40.00g 40.00g vg_rhel6501 1 2 0 wz--n- 49.51g 0 [root@rhel65-03 nova]# vgchange -a y cinder-volumes 0 logical volume(s) in volume group "cinder-volumes" now active Boot from Image(Create Volume) Error in volume.log 2015-02-04 14:12:20.961 21245 ERROR cinder.volume.drivers.ibm.storwize_svc.helpers [req-a9780d29-e87f-46af-9f28-7f27a55c7b17 2c37f6bd55b8402bae2ab04402562e4f 4cf6d19846284f4bb5cb3731395de51b - - -] create_host: No initiators or wwpns supplied. 2015-02-04 14:12:20.962 21245 ERROR cinder.volume.driver [req-a9780d29-e87f-46af-9f28-7f27a55c7b17 2c37f6bd55b8402bae2ab04402562e4f 4cf6d19846284f4bb5cb3731395de51b - - -] Unable to fetch connection information from backend: create_host: No initiators or wwpns supplied. 2015-02-04 14:12:20.964 21245 ERROR cinder.volume.flows.manager.create_volume [req-a9780d29-e87f-46af-9f28-7f27a55c7b17 2c37f6bd55b8402bae2ab04402562e4f 4cf6d19846284f4bb5cb3731395de51b - - -] Failed to copy image 744788c2-7783-46d5-973b-c6fc549f9874 to volume: 4a3ddb09-6342-4cfc-96c5-03e6fff93c36, error: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: create_host: No initiators or wwpns supplied. 2015-02-04 14:12:20.967 21245 WARNING cinder.volume.manager [req-a9780d29-e87f-46af-9f28-7f27a55c7b17 2c37f6bd55b8402bae2ab04402562e4f 4cf6d19846284f4bb5cb3731395de51b - - -] Task 'cinder.volume.flows.manager.create_volume.CreateVolumeFromSpecTask;volume:create' (9342ce99-ef5c-4f2f-a9ee-bc115f8aa6b6) transitioned into state 'FAILURE' EDIT ATTACHMENT (cinder volume to nova instance) error in volume.log: 2015-02-04 16:53:52.594 21245 INFO cinder.volume.manager [-] Updating volume replication status. 2015-02-04 16:54:16.010 21245 ERROR cinder.volume.drivers.ibm.storwize_svc [req-7537dce4-fa77-4abe-9e3f-22d98fd83133 2c37f6bd55b8402bae2ab04402562e4f fa6f9dd011df404b963141baf7547181 - - -] The connector does not contain the required information. 2015-02-04 16:54:16.012 21245 ERROR cinder.volume.manager [req-7537dce4-fa77-4abe-9e3f-22d98fd83133 2c37f6bd55b8402bae2ab04402562e4f fa6f9dd011df404b963141baf7547181 - - -] Unable to fetch connection information from backend: The connector does not contain the required information. 2015-02-04 16:54:16.056 21245 ERROR oslo.messaging.rpc.dispatcher [req-7537dce4-fa77-4abe-9e3f-22d98fd83133 2c37f6bd55b8402bae2ab04402562e4f fa6f9dd011df404b963141baf7547181 - - -] Exception during message handling: Bad or unexpected response from the storage volume backend API: Unable to fetch connection information from backend: The connector does not contain the required information. 2015-02-04 16:54:16.056 21245 TRACE oslo.messaging.rpc.dispatcher Traceback (most recent call last):

Your missing info in your Fibre Channel configuration for the IBM Storwize driver, or the Storwize FC driver is flat out busted (I suspect it's a config issue). You will likely have better luck working with IBM support but if you don't have any luck I'll see if I can find a driver maintainer from IBM to help out. Ahh... so I didn't realize, not only is the FC and StorWize, but also ESX as your hypervisor. So all I can think of is to ensure FC connectivity between your ESX nodes and your FC storage backend. I'll downvote this on my own now that there are more details here.