Ask Your Question
0

Cinder create volume hangs/stuck (no error msg in logs)

asked 2013-03-05 10:25:52 -0500

karel-striegel gravatar image

My problem: When launching on the cinder node the command : cinder create 1 the command "hangs" and keeps hanging without providing a single error msg on the screen or in any log file. When I open another terminal and run cinder list is see the new volume, with state 'creating'. The only way to recover is by existing the command and run a 'cinder delete <id>' after.

My setup : Running latest version of folsom 1 controller node running keystone,nova compute, glance, network 1 compute node running nova compute 1 compute node running nova compute and cinder

Config files of cinder are provided. The cinder logs files have been cleaned before running the command. So they only contain valid entries.

edit retag flag offensive close merge delete

4 answers

Sort by ยป oldest newest most voted
0

answered 2013-03-07 08:56:12 -0500

karel-striegel gravatar image

09:25] <dcz> I've noticed something strange yesterday when I was reinstalling cinder. My database connection string was ignored when I added the line at the end of the cinder.conf [09:25] <dcz> below the section :[keystone_authtoken] [09:26] <dcz> could it be that if I place qpid_hostname below the section [keystone_authtoken] in my cinder.conf that it is ignored ? [09:26] <dcz> ow fuck [09:26] <dcz> that was the problem [09:27] <dcz> it is working now :D [09:27] <winston-d> DCZ: :) you were mixing api-paste.ini content into cinder.conf

edit flag offensive delete link more
0

answered 2013-03-07 07:24:22 -0500

karel-striegel gravatar image

My config files can be found here : https://bugs.launchpad.net/bugs/1146550

edit flag offensive delete link more
0

answered 2013-03-07 07:23:40 -0500

karel-striegel gravatar image

PV VG Fmt Attr PSize PFree /dev/sda5 VolGroup00 lvm2 a-- 687,78g 651,78g /dev/sdb cinder-volumes lvm2 a-- 931,51g 931,51g /dev/sdc cinder-volumes lvm2 a-- 931,51g 931,51g /dev/sdd cinder-volumes lvm2 a-- 698,63g 698,63g /dev/sde cinder-volumes lvm2 a-- 931,51g 931,51g /dev/sdf cinder-volumes lvm2 a-- 931,51g 931,51g

vgs VG #PV #LV #SN Attr VSize VFree VolGroup00 1 5 0 wz--n- 687,78g 651,78g cinder-volumes 5 0 0 wz--n- 4,32t 4,32t

When running the create command no logical volume is created. (I am, manually, able to create a 5G lv in the vg cinder-volumes)

root@OpenStackNode2 /var/log/cinder$ cinder list +--------------------------------------+----------+--------------+------+-------------+-------------+ | ID | Status | Display Name | Size | Volume Type | Attached to | +--------------------------------------+----------+--------------+------+-------------+-------------+ | 43500252-845d-41c8-bf65-ab65650863f6 | creating | test-volume | 5 | None | | +--------------------------------------+----------+--------------+------+-------------+-------------+

Output of the create command with the debug turn on :

root@OpenStackNode2 /var/log/cinder$ cinder --debug create 1 connect: (172.16.41.166, 35357) *** send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 172.16.41.166:35357\r\nContent-Length: 101\r\ncontent-type: application/json\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nuser-agent: python-cinderclient\r\n\r\n' send: '{"auth": {"tenantName": "demo", "passwordCredentials": {"username": "admin", "password": ""}}}' reply: 'HTTP/1.1 200 OK\r\n' header: Vary: X-Auth-Token header: Content-Type: application/json header: Content-Length: 2749 header: Date: Tue, 05 Mar 2013 10:34:44 GMT connect: (172.16.41.168, 8776) ***** send: u'POST /v1/26568729f86f4bb18359fc800ef207c3/volumes HTTP/1.1\r\nHost: 172.16.41.168:8776\r\nContent-Length: 265\r\nx-auth-project-id: demo\r\naccept-encoding: gzip, deflate\r\naccept: application/json\r\nx-auth-token: 46bf3196b5b946879022d147e31d9f5a\r\nuser-agent: python-cinderclient\r\ncontent-type: application/json\r\n\r\n' send: '{"volume": {"status": "creating", "availability_zone": null, "display_description": null, "snapshot_id": null, "user_id": null, "size": 1, "display_name": null, "imageRef": null, "attach_status": "detached", "volume_type": null, "project_id": null, "metadata": {}}}'

Some extra information, my scheduler.log remains untouched. Only when I restart the cinder-scheduler service is sees some activity

fyi : the behavior remains the same when I use the python-novaclient instead of the python-cinderclient : "nova volume-create --display_name vol0 10"

edit flag offensive delete link more
0

answered 2013-03-06 09:23:37 -0500

karel-striegel gravatar image

The version of cinder that I'm using :

Installed Packages Name : openstack-cinder Arch : noarch Version : 2012.2.1 Release : 1.el6 Size : 67 k Repo : installed From repo : epel Summary : OpenStack Volume service

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

1 follower

Stats

Asked: 2013-03-05 10:25:52 -0500

Seen: 250 times

Last updated: Mar 07 '13