Ask Your Question
1

Volume-attach fails - ERROR No initiators or wwpns supplied.

asked 2015-02-03 13:30:05 -0500

zetret gravatar image

updated 2015-02-04 15:59:06 -0500

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):
edit retag flag offensive close merge delete

Comments

Can you launch an instance using 'Boot from image (creates a new volume)'? Be sure that you have large enough space available for the new volume.

I've had issues with cinder whereby volumes will not attach to instances until I first create an instance with volume.

mickt gravatar imagemickt ( 2015-02-04 05:46:56 -0500 )edit

Also, subsequent volumes attach fine but volumes created prior to the above step never attach so I just deleted them.

mickt gravatar imagemickt ( 2015-02-04 05:58:19 -0500 )edit

I have edited the question to reflect what you asked. I've also posted new errors in volume log. Please take a look. Thanks.

zetret gravatar imagezetret ( 2015-02-04 13:16:09 -0500 )edit

5 answers

Sort by ยป oldest newest most voted
0

answered 2015-02-09 00:43:13 -0500

zetret gravatar image

Solved this issue by using iSCSI instead of FC.

edit flag offensive delete link more

Comments

That's not much of a 'solution' to the problem. Did you even try the suggestions?

walter-boring gravatar imagewalter-boring ( 2015-02-10 10:00:12 -0500 )edit
1

answered 2015-02-05 12:10:05 -0500

walter-boring gravatar image

If this is for FibreChannel: 1) You need to make sure you have the kernel driver/module loaded for your FC HBA card. This is typically lpfc for Emulex cards 2) You need to have systool installed. For ubuntu, this is in the sysfsutils package (Verify that it's there by running 'sudo systool -c fc_host -v'

edit flag offensive delete link more
0

answered 2015-02-05 11:48:39 -0500

jgriffith gravatar image

updated 2015-02-05 12:38:00 -0500

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.

edit flag offensive delete link more
0

answered 2015-10-28 12:21:39 -0500

kishore gravatar image

I am running into similar issue. It seems the if you use the UUID of an existing cinder volume and UUID of an existing instance using (cinder::Attachment), it is able to attach the volume with no issues.

example : heat_template_version: 2013-05-23

description: server template for vMMSC

resources: mylab_volume_attachment: type: OS::Cinder::VolumeAttachment properties: volume_id: 65065128-98d4-41ae-8a46-3b07bc64b73f instance_uuid: fae3c718-c031-4a2e-be8c-f876ef2479fd

But if I use Nova::Server and Cinder::Attachment and try to pass the cinder name and instance name via environmental file, it is expecting to create a new volume and new instance.

edit flag offensive delete link more
0

answered 2015-12-10 05:34:09 -0500

I have same problem,i using FC but i cannot upload image to volume. Can you help me ?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

2 followers

Stats

Asked: 2015-02-03 13:30:05 -0500

Seen: 1,855 times

Last updated: Dec 10 '15