Ask Your Question

Cinder LVM Issue

asked 2013-12-30 12:28:49 -0500

mili gravatar image


When I create a volume the status of the newly created volume is Error. The volume gets created but not useable as error status. I can also successfully delete the volume.

Topology: Havana, ubuntu 12.0.4 I have a MD3600 Dell San, It is directly connected to a ubuntu server(block1) which has cinder installed. the drives from the SAN are mounted to the block1. The issue looks like a race condition to me, There is bug reported I checked my and I have the break in the loop.

Please help me on what I should do to fix this.

If this is not the best approach to use my san as my storage or you think i can use a better solution to provide storage for vms please advise.

Cheers cinder.conf

#RabbitMQ Configuration rpc_backend = cinder.openstack.common.rpc.impl_kombu rabbit_host = controller rabbit_port = 5672 rabbit_userid = guest rabbit_password = ***

Glance Configuration

glance_host = controller

rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper = tgtadm service_host = controller enabled_backends=lvmdriver-1,lvmdriver-2,lvmdriver-3 [lvmdriver-1] volume_group=cinder-volumes1 volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver volume_backend_name=LVM_iSCSI [lvmdriver-2] volume_group=cinder-volumes2 volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver volume_backend_name=LVM_iSCSI [lvmdriver-3] volume_group=cinder-volumes3 volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver volume_backend_name=LVM_iSCSI_b verbose = True auth_strategy = keystone state_path = /var/lib/cinder lock_path = /var/lock/cinder volumes_dir = /var/lib/cinder/volumes


The SQLAlchemy connection string used to connect to the

database (string value)

connection = mysql://cinder:***@controller/cinder

Cinder-Volume LOG: 2013-12-30 17:57:43.335 4760 WARNING cinder.quota [req-a15eb7b8-15d5-48ec-8b09-ae9236de90a4 d501dfde00d945a0938cfdb77eb6db1b ee779790a60f4594ad423310c232fff2] Deprecated: Default quota for resource: volumes is set by the default quota flag: quota_volumes, it is now deprecated. Please use the the default quota class for default quota. 2013-12-30 17:58:46.312 4760 WARNING cinder.taskflow.utils [-] Activating 5 rollbacks due to <cinder.taskflow.utils.flowfailure 0x2d90c50="" at="" object="">. 2013-12-30 17:58:46.340 4760 ERROR cinder.volume.flows.create_volume [req-8a0cb45e-c402-4bf6-8f42-4589d7ccf72a d501dfde00d945a0938cfdb77eb6db1b ee779790a60f4594ad423310c232fff2] Unexpected build error: 2013-12-30 17:58:46.340 4760 TRACE cinder.volume.flows.create_volume Traceback (most recent call last): 2013-12-30 17:58:46.340 4760 TRACE cinder.volume.flows.create_volume File "/usr/lib/python2.7/dist-packages/cinder/taskflow/patterns/", line 172, in run_it 2013-12-30 17:58:46.340 4760 TRACE cinder.volume.flows.create_volume result = runner(context, args, *kwargs) 2013-12-30 17:58:46.340 4760 TRACE cinder.volume.flows.create_volume File "/usr/lib/python2.7/dist-packages/cinder/taskflow/", line 260, in __call__ 2013-12-30 17:58:46.340 4760 TRACE cinder.volume.flows.create_volume self.result = self.task(args, *kwargs) 2013-12-30 17:58:46.340 4760 TRACE cinder.volume.flows.create_volume File "/usr/lib/python2.7/dist-packages/cinder/volume/flows/create_volume/", line 1520, in __call__ 2013-12-30 17:58:46.340 4760 TRACE cinder.volume.flows.create_volume model_update = self.driver.create_export(context, volume_ref) 2013-12-30 17:58:46.340 4760 TRACE cinder.volume.flows.create_volume File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/", line 585, in create_export ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2013-12-30 13:04:17 -0500

SamYaple gravatar image

Can you verify the volume was created in LVM? lvdisplay cinder-volumes1

I had this exact error in a dev setup a while back. The volume was created successfully, but it would retry the creation as if it had failed. When the second creation was attempted, it _did_ fail because it already existed.

Was this configuration working before you added multiple-backends?

edit flag offensive delete link more


SamYaple you are the best and a pro both in Cinder and neutron I hope I can use your help with neutron too ;) It works after I removed the muti-backend configuration. But now how can I use my other volumes?

mili gravatar imagemili ( 2013-12-30 13:39:08 -0500 )edit

Run `cinder extra-specs-list` and verify you actually created the extra types. Assuming you didn'tyou'll need to create your extra types, you may have missed a few commands If you did, just remove everything and try again.See .

SamYaple gravatar imageSamYaple ( 2013-12-30 13:46:44 -0500 )edit

answered 2014-03-18 02:20:38 -0500

kamlesh gravatar image

tgt services get lost after rebooting and give error during volume creation in openstack.You can then see your volume group there with the help of #vgs. Once you reboot even after reflecting it in vgs you need to change iscsi helper to tgtdm in /etc/cinder/cinder.conf file. At the end restart the cinder service...then you can use ur volume as status will become avialble.try this i did this n now m able to use volume

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


Asked: 2013-12-30 12:28:49 -0500

Seen: 929 times

Last updated: Mar 18 '14