Ask Your Question
0

OpenStack Kilo, Cinder can't create snapshots: lvm volume not found

asked 2016-05-11 07:53:25 -0500

animaletdesequia gravatar image

updated 2016-05-12 03:22:21 -0500

We have deployed OpenStack Kilo on Ubuntu 14.04 using Mirantis OS fuel 7.0. We have a setup with 3 controller/storage nodes and 3 compute nodes, all connected for high availability through haproxy.

After some problems with the storage (we're using a multi-backend based on Cinder/LVM volumes on the controllers plus a NetApp NFS shared storage) we've managed to get volume creation, expanding, deletion, attachment, detachment etc.

The problem is when we try to create an snapshot of one of the volumes stored in cinder_iscsi backend. We get this, on the controller that's trying to create the snapshot through the web interface:

   root@node-01:~# tail -f /var/log/cinder-all.log | grep -v "cinder-api"
<158>May 11 11:28:17 Nefeles001 cinder-volume 2016-05-11 11:28:17.294 92341 INFO cinder.volume.manager [req-a79a8998-70f7-4b9d-b1d1-68f8a04e5399 2d60663e49a74eca9f0a96dc713154c5 2a1b8d6fd53045dd8acc8b09c292cb9f - - -] snapshot c4d32012-38ca-4ba8-bca2-186d5703620d: creating
<158>May 11 11:28:17 Nefeles001 cinder-volume 2016-05-11 11:28:17.836 92341 INFO cinder.brick.local_dev.lvm [req-a79a8998-70f7-4b9d-b1d1-68f8a04e5399 2d60663e49a74eca9f0a96dc713154c5 2a1b8d6fd53045dd8acc8b09c292cb9f - - -] Logical Volume not found when querying LVM info. (vg_name=cinder, lv_name=volume-3f253a13-7f12-46fb-bec5-df70b80d9d9c
<155>May 11 11:28:17 Nefeles001 cinder-volume 2016-05-11 11:28:17.836 92341 ERROR cinder.brick.local_dev.lvm [req-a79a8998-70f7-4b9d-b1d1-68f8a04e5399 2d60663e49a74eca9f0a96dc713154c5 2a1b8d6fd53045dd8acc8b09c292cb9f - - -] Trying to create snapshot by non-existent LV: volume-3f253a13-7f12-46fb-bec5-df70b80d9d9c
<155>May 11 11:28:17 Nefeles001 cinder-volume 2016-05-11 11:28:17.861 92341 ERROR oslo_messaging.rpc.dispatcher [req-a79a8998-70f7-4b9d-b1d1-68f8a04e5399 2d60663e49a74eca9f0a96dc713154c5 2a1b8d6fd53045dd8acc8b09c292cb9f - - -] Exception during message handling: Volume device not found at volume-3f253a13-7f12-46fb-bec5-df70b80d9d9c.
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last):
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 142, in _dispatch_and_reply
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher     executor_callback))
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 186, in _dispatch
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher     executor_callback)
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 130, in _do_dispatch
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher     result = func(ctxt, **new_args)
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 105, in wrapper
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher     return f(*args, **kwargs)
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 662, in create_snapshot
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher     snapshot.save(context)
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 85, in __exit__
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher     six.reraise(self.type_, self.value, self.tb)
2016-05-11 11:28:17.861 92341 TRACE oslo_messaging.rpc.dispatcher   File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 654, in create_snapshot ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-08-30 06:58:48 -0500

bishoy gravatar image

I don't think it can be really worked automatically as LVM is not really a shared storage.

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

Stats

Asked: 2016-05-11 07:53:25 -0500

Seen: 434 times

Last updated: Aug 30 '16