Cinder create fails with "VolumeNotFound" [closed]

asked 2013-06-10 05:02:55 -0600

ugo184 gravatar image

updated 2013-06-10 14:25:08 -0600

smaffulli gravatar image

Hello there,

I have been trying unsuccessfully to create volumes with cinder.

So here is how I proceeded:

  1. All components of Grizzly are installed (except Quantum which is still a work in progress). Everything seems to work fine so far.
  2. To install Cinder, I followed the official procedure:
  3. Database is installed on Cinder host, while the other services keystone, glance, etc are on the controller node.
  4. Database sync worked fine, and it created all the tables needed.
  5. Creating the volume however let the volume in a 'creating' state and reports errors

Here is my report:

Display of pvs/vgs and directories for cinder:

# pvs
  PV         VG             Fmt  Attr PSize  PFree 
  /dev/sda2  cinder-volumes lvm2 a-   51,22g 51,22g
# vgs
  VG             #PV #LV #SN Attr   VSize  VFree 
  cinder-volumes   1   0   0 wz--n- 51,22g 51,22g
# ls -lR /var/lib/cinder/ 
total 52
-rw------- 1 cinder cinder 41984 juin   7 16:34 cinder.sqlite
drwxr-x--- 2 cinder cinder  4096 mai   17 22:18 volumes

total 0

Creating the first volume on cinder:
# cinder create --display_name test-cinder1
|       Property      |                Value                 |
|     attachments     |                  []                  |
|  availability_zone  |                 nova                 |
|       bootable      |                false                 |
|      created_at     |      2013-06-10T09:33:36.233022      |
| display_description |                 None                 |
|     display_name    |             test-cinder              |
|          id         | f5ec7252-a9de-448c-b7a6-8d9d7814d860 |
|       metadata      |                  {}                  |
|         size        |                  1                   |
|     snapshot_id     |                 None                 |
|     source_volid    |                 None                 |
|        status       |               creating               |
|     volume_type     |                 None                 |

The output on Cinder-node concerning the schedule:

# tail -f /var/log/cinder/cinder-scheduler.log 
2013-06-10 11:33:39    ERROR [cinder.scheduler.manager] Failed to schedule_create_volume: Volume f5ec7252-a9de-448c-b7a6-8d9d7814d860 could not be found. 
2013-06-10 11:33:39    ERROR [root] Original exception being dropped: ['Traceback (most recent call last):\n', '  File "/usr/lib/python2.7/dist-packages/cinder/scheduler/", line 104, in create_volume\n    self.driver.schedule_create_volume(context, request_spec,\n', '  File "/usr/lib/python2.7/dist-packages/cinder/scheduler/", line 77, in schedule_create_volume\n    updated_volume = driver.volume_update_db(context, volume_id, host)\n', '  File "/usr/lib/python2.7/dist-packages/cinder/scheduler/", line 53, in volume_update_db\n    return db.volume_update(context, volume_id, values)\n', '  File "/usr/lib/python2.7/dist-packages/cinder/db/", line 268, in volume_update\n    return IMPL.volume_update(context, volume_id, values)\n', '  File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/", line 123, in wrapper\n    return f(args, *kwargs)\n', '  File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/", line 1103, in volume_update\n    volume_ref = volume_get(context, volume_id, session=session)\n', '  File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/", line 123, in wrapper\n    return f(args, *kwargs)\n', '  File "/usr/lib/python2.7/dist-packages/cinder/db/sqlalchemy/", line 1023, in volume_get\n    raise exception.VolumeNotFound(volume_id=volume_id)\n', 'VolumeNotFound: Volume f5ec7252-a9de-448c-b7a6-8d9d7814d860 could not be found.\n'] 
2013-06-10 11:33:39    ERROR [cinder.openstack.common.rpc.amqp] Exception during message handling 
Traceback (most recent call last): 
  File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/", line 430, in _process_data 
    rval = self.proxy.dispatch(ctxt, version, method, *args) 
  File "/usr/lib/python2.7/dist-packages ...
edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by smaffulli
close date 2013-06-10 14:25:36.035235

1 answer

Sort by ยป oldest newest most voted

answered 2013-06-10 09:02:17 -0600

ugo184 gravatar image

updated 2013-06-10 14:25:55 -0600

smaffulli gravatar image

Back again, for the follow up

It seems that I hadn't understand the documentation correctly with what I was trying to achieve. I restarted the installation by splitting the services cinder-volume on my dedicated cinder-node and putting the remaining cinder-api/cinder-scheduler on my controller node.

I'm still facing some issues, but at least I'm progressing in the setup. Will try to keep you up to date.


After few configurations, I have now solved my problem. I'm able to create instance from my controller on my cinder-node without issue.

To help out those who might want to set up their Grizzly the same way, here is how the services are split:
-Controler-node: db/cinder-scheduler/cinder-api
-Cinder-node: tgt/cinder-volume

You then have to setup:
1. The connection to the mysql db from the Cinder-node (cinder.conf) to the Controller-node (Don't forget user on the controller-node).
2. Add iscsi_ip_address = cinder-public-ip on the Controller's cinder.conf file
3. Restart services and then try to create your volumes.

Hope it helped!

Helpful links:

That's pretty much it

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-06-10 05:02:55 -0600

Seen: 479 times

Last updated: Jun 10 '13