Ask Your Question
1

cinder volume stuck in creating

asked 2015-02-16 14:03:15 -0600

Jaco.Minnaar gravatar image

updated 2015-04-07 06:35:34 -0600

SGPJ gravatar image

After creating new cinder volume (cinder create --display-name vt1 --volume-type lvm 1), cinder list dislays "creating" but never becomes available.

No errors in volume or scheduler log, rabbitmq running and both controller and block hosts connected.

cinder list output:

[root@controll1 ~]# cinder list
+--------------------------------------+----------+--------------+------+-------------+----------+-------------+
|                  ID                  |  Status  | Display Name | Size | Volume Type | Bootable | Attached to |
+--------------------------------------+----------+--------------+------+-------------+----------+-------------+
| 764e80bb-e001-47ba-b76f-657c6864de87 | creating |     vt1      |  1   |     lvm     |  false   |             |
+--------------------------------------+----------+--------------+------+-------------+----------+-------------+

Schedule Log:
2015-02-16 20:24:27.715 10957 INFO cinder.service [-] Starting cinder-scheduler node (version 2014.2.1)
2015-02-16 20:24:27.717 10957 INFO oslo.messaging._drivers.impl_rabbit [req-ab0394d8-6a82-4feb-be21-7fd0bc4c76a7 - - - - -] Connecting to AMQP server on controll1:5672
2015-02-16 20:24:27.736 10957 INFO oslo.messaging._drivers.impl_rabbit [req-ab0394d8-6a82-4feb-be21-7fd0bc4c76a7 - - - - -] Connected to AMQP server on controll1:5672
2015-02-16 20:24:28.116 10957 INFO oslo.messaging._drivers.impl_rabbit [-] Connecting to AMQP server on controll1:5672
2015-02-16 20:24:28.128 10957 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on controll1:5672

Api Log: 2015-02-16 20:24:28.147 10956 INFO cinder.wsgi [-] osapi_volume listening on 0.0.0.0:8776 2015-02-16 20:24:28.147 10956 INFO cinder.openstack.common.service [-] Starting 4 workers 2015-02-16 20:24:28.153 10956 INFO cinder.openstack.common.service [-] Started child 10974 2015-02-16 20:24:28.155 10974 INFO eventlet.wsgi.server [-] (10974) wsgi starting up on http://0.0.0.0:8776/ 2015-02-16 20:24:28.159 10956 INFO cinder.openstack.common.service [-] Started child 10975 2015-02-16 20:24:28.162 10975 INFO eventlet.wsgi.server [-] (10975) wsgi starting up on http://0.0.0.0:8776/ 2015-02-16 20:24:28.166 10956 INFO cinder.openstack.common.service [-] Started child 10976 2015-02-16 20:24:28.169 10976 INFO eventlet.wsgi.server [-] (10976) wsgi starting up on http://0.0.0.0:8776/ 2015-02-16 20:24:28.173 10956 INFO cinder.openstack.common.service [-] Started child 10977 2015-02-16 20:24:28.176 10977 INFO eventlet.wsgi.server [-] (10977) wsgi starting up on http://0.0.0.0:8776/ 2015-02-16 20:36:34.493 10977 INFO eventlet.wsgi.server [-] (10977) accepted ('172.16.200.21', 42411) 2015-02-16 20:36:34.922 10977 INFO cinder.api.openstack.wsgi [req-f517e2ab-f302-4c0b-8094-47fee398b709 52415487a1d845f4afddebf8ecf204ff 5b79b126fd6d41a6b3c336007ee1beb1 - - -] GET http://controll1:8776/v1/5b79b126fd6d... 2015-02-16 20:36:35.145 10977 WARNING cinder.quota [req-f517e2ab-f302-4c0b-8094-47fee398b709 52415487a1d845f4afddebf8ecf204ff 5b79b126fd6d41a6b3c336007ee1beb1 - - -] De precated: Default quota for resource: backups is set by the default quota flag: quota_backups, it is now deprecated. Please use the default quota class for default quot a. 2015-02-16 20:36:35.146 10977 WARNING cinder.quota [req-f517e2ab-f302-4c0b-8094-47fee398b709 52415487a1d845f4afddebf8ecf204ff 5b79b126fd6d41a6b3c336007ee1beb1 - - -] De precated: Default quota for resource: backup_gigabytes is set by the default quota flag: quota_backup_gigabytes, it is now deprecated. Please use the default quota clas s for default quota. 2015-02-16 20:36:35.161 10977 INFO cinder.api.openstack.wsgi [req-f517e2ab-f302-4c0b-8094-47fee398b709 52415487a1d845f4afddebf8ecf204ff 5b79b126fd6d41a6b3c336007ee1beb1 - - -] http://controll1:8776/v1/5b79b126fd6d... returned with HTTP 200 2015-02-16 20:36:35.162 10977 INFO eventlet.wsgi.server [req-f517e2ab-f302-4c0b-8094-47fee398b709 52415487a1d845f4afddebf8ecf204ff 5b79b126fd6d41a6b3c336007ee1beb1 - - -] 172.16.200.21 - - [16/Feb/2015 20:36:35] "GET /v1/5b79b126fd6d41a6b3c336007ee1beb1/limits HTTP/1.1" 200 541 0.667582 ... (more)

edit retag flag offensive close merge delete
add a comment

3 answers

Sort by ยป oldest newest most voted
1

answered 2015-03-11 10:39:42 -0600

Jaco.Minnaar gravatar image

Stop all cinder services (on control node and cinder node), log onto rabitmq manger and delete anything containing cinder. Start services again and try to re create volume - problem solved....

edit flag offensive delete link more
add a comment
0

answered 2015-04-01 07:39:33 -0600

ethode gravatar image

I was getting the same messages.. Wound up that on my controller node 'nova-scheduler' and 'nova-compute' where not running, I started those services and everything was happy.

edit flag offensive delete link more
add a comment
0

answered 2015-02-16 17:46:25 -0600

schegi gravatar image

You would not need the volume-type parameter in cinder create. This is only needed if you are running multiple cinder backends. And the volume-types have to be created seperately like described here.

If you are running multiple backends you should check if the volume types are set properly. This causes me some trouble.

Stefan

edit flag offensive delete link more

Comments

Hi Stefan,

I added this after the default config did not work and to resolve an error in the volume log regarding LVMISCSIDriver not being loaded.

This is not causing the creating task to hang though, it was stuck in creating even without this aditional config.

Do have any other advise ?

Jaco.Minnaar gravatar imageJaco.Minnaar ( 2015-02-16 23:09:40 -0600 )edit

could you please post the output of 'cinder type-list' and 'cinder extra-specs-list'.

schegi gravatar imageschegi ( 2015-02-17 06:45:45 -0600 )edit

[root@controll1 ~]# cinder type-list +--------------------------------------+------+ | ID | Name | +--------------------------------------+------+ | 013fef4b-e7d7-4c22-93c8-c19e12d02619 | lvm | +--------------------------------------+------+

Jaco.Minnaar gravatar imageJaco.Minnaar ( 2015-02-17 11:01:55 -0600 )edit

[root@controll1 ~]# cinder extra-specs-list | ID | Name | extra_specs | | 013fef4b-e7d7-4c22-93c8-c19e12d02619 | lvm | {u'volume_backend_name': u'LVM_iSCSI'} |

Jaco.Minnaar gravatar imageJaco.Minnaar ( 2015-02-17 11:02:52 -0600 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2015-02-16 14:03:15 -0600

Seen: 914 times

Last updated: Apr 07 '15

Related questions

cinder nfs snapshot create and delete fail (No JSON object could be decoded)

HTTPInternalServerError(500) if create volume from image [closed]

storage node

Re-initializing or dynamically configuring cinder driver?

volume usage hour

cinder volumes not attached to controller

Issue with creating a volume from image via cinder

what does "source volid" mean in Cinder? [closed]

Migration attached volume between cinder pools

Problem Creating Volume Backups