Ask Your Question
0

cinder LVMISCSIDriver Unable to update stats, driver is uninitialized [closed]

asked 2014-01-13 07:42:12 -0600

mili gravatar image

updated 2014-01-13 10:10:55 -0600

Hi,

I'm having couple of issues with Cinder, but first and foremost its the below issue, I sometimes can create a volume and sometimes cant:

Here is what I'm getting in cinder-volume log:

2014-01-13 13:31:25.746 1364 TRACE cinder.openstack.common.rpc.amqp
2014-01-13 13:32:08.646 1364 INFO cinder.volume.manager [-] Updating volume status
2014-01-13 13:32:08.647 1364 WARNING cinder.volume.manager [-] Unable to update stats, driver is uninitialized
2014-01-13 13:32:57.307 1364 ERROR cinder.openstack.common.rpc.amqp [req-cadfbb08-bc8f-4759-b4d4-973621b9f77b a015544687d5405dbdcfbf0522d3ea3b de8d94a92a114774b28e0d2ffd25101b] Exception during message handling
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp Traceback (most recent call last):
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/amqp.py", line 441, in _process_data
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp     **args)
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/cinder/openstack/common/rpc/dispatcher.py", line 148, in dispatch
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp     return getattr(proxyobj, method)(ctxt, **kwargs)
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/cinder/utils.py", line 807, in wrapper
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp     raise exception.DriverNotInitialized(driver=driver_name)
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp DriverNotInitialized: Volume driver 'LVMISCSIDriver' not initialized.
2014-01-13 13:32:57.307 1364 TRACE cinder.openstack.common.rpc.amqp
2014-01-13 13:33:08.648 1364 INFO cinder.volume.manager [-] Updating volume status
2014-01-13 13:33:08.648 1364 WARNING cinder.volume.manager [-] Unable to update stats, driver is uninitialized
2014-01-13 13:34:08.649 1364 INFO cinder.volume.manager [-] Updating volume status
2014-01-13 13:34:08.649 1364 WARNING cinder.volume.manager [-] Unable to update stats, driver is uninitialized
2014-01-13 13:35:08.650 1364 INFO cinder.volume.manager [-] Updating volume status
2014-01-13 13:35:08.650 1364 WARNING cinder.volume.manager [-] Unable to update stats, driver is uninitialized

The other issue that I have is for when the cinder service is Magically working but I'm not able to boot from image(create a new volume) i get no image error, the system creates the volume 3 times and the instance fails.

The above issue looks to be resolved by adding the driver in cinder.conf but i have the below issue now: 1-When I create or delete a small size volume everything seems to be ok, but deleten time is very long(1gig volume). But when I create a large volume(200GB) I cannot delete the volume at all or it takes forever, there in no log for this in schdular, there is below long in cinder-api and this log in cinder-volume:

Another issue as before is not being able to boot from volume(no ... (more)

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by mili
close date 2014-02-13 07:17:05.145378

add a comment

1 answer

Sort by ยป oldest newest most voted
2

answered 2014-01-13 10:24:13 -0600

jgriffith gravatar image

updated 2014-01-13 10:45:00 -0600

You have an awful lot going on here, it sounds like you've addressed the issue of the volume driver not being initialized, so I'll jump to the delete issues your describing.

Cinder provides a volume_clear option which by default will dd zeros across the entire lv when you delete it. This unfortunately can take an extremely long time. If you don't need this security, you can set the following in your cinder.conf file to skip it:

volume_clear = none

edit flag offensive delete link more

Comments

volume_clear = none fixed the log deletion time. Thanks

mili gravatar imagemili ( 2014-01-13 10:52:57 -0600 )edit

What is the driver that you added and how did you add it? There are several references to "driver" in the cinder.conf file.

Thank you.

Jeff

jeffsilverman gravatar imagejeffsilverman ( 2014-08-13 11:17:26 -0600 )edit

Hi Jeff

try this

volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver

and restart the cinder-api schedular and volume services if all of them are on same node.

vaibhavhyd2014 gravatar imagevaibhavhyd2014 ( 2015-10-02 10:56:01 -0600 )edit

I have the very same issue and I have the above driver for rbd added correctly but I am not able to create a new volume from the option(create a new volume) from nova and I can confirm that rbd driver is perfectly working fine.

2018-11-17 17:45:40.444 32054 INFO cinder.volume.manager [req-d4d12536-

vgdub gravatar imagevgdub ( 2018-11-17 11:50:34 -0600 )edit
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2014-01-13 07:42:12 -0600

Seen: 9,364 times

Last updated: Jan 13 '14

Related questions

Issue with creating a volume from image via cinder

Migration attached volume between cinder pools

Volume did not finish being created even

dedicated network between cinder and compute

HEAT update failed on block volume operation

Cinder-volume not registered?

error in cinder-volume

Block Device Mapping is Invalid: failed to get image

read only volume can be mounted to an instance or not ?

rdo Hypervisor Summary Disk Usage Used 0 of 49.0GB