The proper Havana release in in the UCA now, so I've upgraded to that. I'm still able to reproduce this. It's simple for me: I'm deploying with the puppet-openstack modules: https://forge.puppetlabs.com/puppetlabs/openstack. I can't think of anything unusual about the setup -- simply don't create a cinder-volumes volume group, and try to make a volume.
cinder-volume will log, at startup:
2013-10-31 11:45:32.311 15709 TRACE cinder.volume.manager Traceback (most recent call last):
2013-10-31 11:45:32.311 15709 TRACE cinder.volume.manager File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 190, in init_host
2013-10-31 11:45:32.311 15709 TRACE cinder.volume.manager self.driver.check_for_setup_error()
2013-10-31 11:45:32.311 15709 TRACE cinder.volume.manager File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py", line 94, in check_for_setup_error
2013-10-31 11:45:32.311 15709 TRACE cinder.volume.manager raise exception.VolumeBackendAPIException(data=message)
2013-10-31 11:45:32.311 15709 TRACE cinder.volume.manager VolumeBackendAPIException: Bad or unexpected response from the storage volume backend API: Volume Group cinder-volumes does not exist
The proper Havana release in in the UCA now, so I've upgraded to that. I'm still able to reproduce this. It's simple for me: I'm deploying with the puppet-openstack modules: https:/ /forge. puppetlabs. com/puppetlabs/ openstack. I can't think of anything unusual about the setup -- simply don't create a cinder-volumes volume group, and try to make a volume.
cinder-volume will log, at startup:
2013-10-31 11:45:32.311 15709 TRACE cinder. volume. manager Traceback (most recent call last): volume. manager File "/usr/lib/ python2. 7/dist- packages/ cinder/ volume/ manager. py", line 190, in init_host volume. manager self.driver. check_for_ setup_error( ) volume. manager File "/usr/lib/ python2. 7/dist- packages/ cinder/ volume/ drivers/ lvm.py" , line 94, in check_for_ setup_error volume. manager raise exception. VolumeBackendAP IException( data=message) volume. manager VolumeBackendAP IException: Bad or unexpected response from the storage volume backend API: Volume Group cinder-volumes does not exist
2013-10-31 11:45:32.311 15709 TRACE cinder.
2013-10-31 11:45:32.311 15709 TRACE cinder.
2013-10-31 11:45:32.311 15709 TRACE cinder.
2013-10-31 11:45:32.311 15709 TRACE cinder.
2013-10-31 11:45:32.311 15709 TRACE cinder.
then when a volume is asked to be created:
2013-10-31 11:46:11.638 15709 ERROR cinder. openstack. common. rpc.amqp [req-70eebc51- fca6-410d- 8caa-9415a4a215 30 b7b8f92e13534c2 bbd32b0ff1b801b 76 a2e59bca1d7a48e b895f4f7806bb89 d6] Exception during message handling openstack. common. rpc.amqp Traceback (most recent call last): openstack. common. rpc.amqp File "/usr/lib/ python2. 7/dist- packages/ cinder/ openstack/ common/ rpc/amqp. py", line 441, in _process_data openstack. common. rpc.amqp **args) openstack. common. rpc.amqp File "/usr/lib/ python2. 7/dist- packages/ cinder/ openstack/ common/ rpc/dispatcher. py", line 148, in dispatch openstack. common. rpc.amqp return getattr(proxyobj, method)(ctxt, **kwargs) openstack. common. rpc.amqp File "/usr/lib/ python2. 7/dist- packages/ cinder/ utils.py" , line 807, in wrapper openstack. common. rpc.amqp raise exception. DriverNotInitia lized(driver= driver_ name) openstack. common. rpc.amqp DriverNotInitia lized: Volume driver 'LVMISCSIDriver' not initialized.
2013-10-31 11:46:11.638 15709 TRACE cinder.
2013-10-31 11:46:11.638 15709 TRACE cinder.
2013-10-31 11:46:11.638 15709 TRACE cinder.
2013-10-31 11:46:11.638 15709 TRACE cinder.
2013-10-31 11:46:11.638 15709 TRACE cinder.
2013-10-31 11:46:11.638 15709 TRACE cinder.
2013-10-31 11:46:11.638 15709 TRACE cinder.
2013-10-31 11:46:11.638 15709 TRACE cinder.
At this point, there's a volume, and it's stuck in "creating", forever:
pfrost@ os-controller01 :~$ cinder list ------- ------- ------- ------- ----+-- ------- -+----- ------- --+---- --+---- ------- --+---- ------+ ------- ------+ ------- ------- ------- ------- ----+-- ------- -+----- ------- --+---- --+---- ------- --+---- ------+ ------- ------+ 5d31-465f- a0c7-9503f845b2 65 | creating | test | 1 | None | false | | ------- ------- ------- ------- ----+-- ------- -+----- ------- --+---- --+---- ------- --+---- ------+ ------- ------+ os-controller01 :~$ cinder show c950bca7- 5d31-465f- a0c7-9503f845b2 65 ------- ------- ------- -----+- ------- ------- ------- ------- ------- --+ ------- ------- ------- -----+- ------- ------- ------- ------- ------- --+ 31T15:46: 11.000000 | 5d31-465f- a0c7-9503f845b2 65 | host-attr: host | os-compute01 | mig-status- attr:migstat | None | mig-status- attr:name_ id | None | tenant- attr:tenant_ id | a2e59bca1d7a48e b895f4f7806bb89 d6 | ------- ------- ------- -----+- ------- ------- ------- ------- ------- --+ os-controller01 :~$ cinder delete c950bca7- 5d31-465f- a0c7-9503f845b2 65
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| c950bca7-
+------
pfrost@
+------
| Property | Value |
+------
| attachments | [] |
| availability_zone | nova |
| bootable | false |
| created_at | 2013-10-
| display_description | |
| display_name | test |
| id | c950bca7-
| metadata | {} |
| os-vol-
| os-vol-
| os-vol-
| os-vol-
| size | 1 |
| snapshot_id | None |
| source_volid | None |
| status | creating |
| volume_type | None |
+------
pfrost@
ERROR: Invalid volume: Volume status must be available or error, but current status is: creating
It can be force-deleted, but then it's just stuck in "deleting" instead of "creating":
pfrost@ os-controller01 :~$ cinder force-delete c950bca7- 5d31-465f- a0c7-9503f845b2 65 os-controller01 :~$ cinder list ------- ------- ------- ------- ----+-- ------- -+----- ------- --+---- --+---- ------- --+---- ------+ ------- ------+ ------- ------- ------- ------- ----+-- ------- -+----- ------- --+---- --+---- ------- --+---- ------+ ------- ------+ 5d31-465f- a0c7-9503f845b2 65 | deleting | test | 1 | None | false | | ------- ------- ------- ------- ----+-- ------- -+----- ------- --+---- --+---- ------- --+---- ------+ ------- ------+
pfrost@
+------
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| c950bca7-
+------
Not sure why else you wouldn't be able to reproduce this, unless it's something that's been fixed very recently. My cinder.conf looks like:
[DEFAULT] rootwrap. conf api-paste. ini name_template = volume-%s cinder/ volumes host=127. 0.0.1 mysql:/ /cinder: xxx@127. 0.0.1/cinder? charset= utf8 config= /etc/cinder/ api-paste. ini userid= openstack listen= 0.0.0.0 timeout= 3600 virtual_ host=/ driver= cinder. scheduler. simple. SimpleScheduler hosts=127. 0.0.1:5672 ha_queues= False cinder. openstack. common. rpc.impl_ kombu
rootwrap_config = /etc/cinder/
api_paste_confg = /etc/cinder/
iscsi_helper = tgtadm
volume_
volume_group = cinder-volumes
verbose = False
auth_strategy = keystone
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
volumes_dir = /var/lib/
rabbit_
sql_connection=
api_paste_
debug=False
rabbit_
osapi_volume_
sql_idle_
rabbit_
scheduler_
rabbit_
rabbit_
rabbit_password=xxx
rabbit_port=5672
rpc_backend=