Shulou(Shulou.com)05/31 Report--

This article mainly shows you "what to do when the cloud disk has been in the deleting state". The content is easy to understand and clear. I hope it can help you solve your doubts. Let the editor lead you to study and learn the article "how to do when the cloud disk has been in the deleting state".

I. background

Due to a problem, when deleting a cloud disk, the status of the cloud disk always deals with the deleting status, and can be deleted normally when the problem is resolved, but the cloud disk dealing with the deleting status still needs to be processed manually.

Second, the process of treatment

Enter the admin management user, click on the cloud disk, and update the status of the cloud disk as an error.

After the status update of the cloud disk is completed, the action on the right will appear to delete the volume. You can click to delete the disk.

Check the log in addition

# view volume.log 2017-04-05 14 most recent call last 07VR 42.108 5603 TRACE oslo_messaging.rpc.dispatcher Traceback (most recent call last): 2017-04-05 147VR 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line In _ dispatch_and_reply2017-04-05 14 TRACE oslo_messaging.rpc.dispatcher executor_callback 07 TRACE oslo_messaging.rpc.dispatcher executor_callback 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 1886) In _ dispatch2017-04-05 14 TRACE oslo_messaging.rpc.dispatcher executor_callback 07 TRACE oslo_messaging.rpc.dispatcher executor_callback 42.108 5603 TRACE oslo_messaging.rpc.dispatcher result = func (ctxt) 42.108 5603 TRACE oslo_messaging.rpc.dispatcher result = func * * new_args) 2017-04-05 14 usr/lib/python2.7/site-packages/osprofiler/profiler.py 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib/python2.7/site-packages/osprofiler/profiler.py", line 105, in wrapper2017-04-05 14 usr/lib/python2.7/site-packages/osprofiler/profiler.py 42.108 5603 TRACE oslo_messaging.rpc.dispatcher return f (* args, * * kwargs) 2017-04-05 2017-04-05 14 Swiss 07 line 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib/python2.7/site-packages/cinder/volume/manager.py" Line 5603 TRACE oslo_messaging.rpc.dispatcher return lvo_inner2 (inst, context, volume_id, * * kwargs) 2017-04-05 147 TRACE oslo_messaging.rpc.dispatcher return lvo_inner2 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 439, in inner2017-04-05 1415 07Switzerland 42.108 5603 TRACE oslo_messaging.rpc.dispatcher do_log=False, semaphores=semaphores Delay=delay): 2017-04-05 147 usr/lib64/python2.7/contextlib.py 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib64/python2.7/contextlib.py", line 17, in _ _ enter__2017-04-05 1415 42.108 5603 TRACE oslo_messaging.rpc.dispatcher return self.gen.next () 2017-04-05 2017-04-05 14 usr/lib64/python2.7/contextlib.py 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line In lock2017-04-05 14 delay=delay 07 TRACE oslo_messaging.rpc.dispatcher File 42.108 5603 TRACE oslo_messaging.rpc.dispatcher ext_lock.acquire (delay=delay) 2017-04-05 147 delay=delay 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py" In acquire2017-04-05 14 basedir 07 TRACE oslo_messaging.rpc.dispatcher File 42.108 5603 TRACE oslo_messaging.rpc.dispatcher fileutils.ensure_tree (basedir) 2017-04-05 147 basedir 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib/python2.7/site-packages/oslo_concurrency/openstack/common/fileutils.py", line 35 In ensure_tree2017-04-05 14 path 07 path 42.108 5603 TRACE oslo_messaging.rpc.dispatcher os.makedirs (path) 2017-04-05 14V 07V 42.108 5603 TRACE oslo_messaging.rpc.dispatcher File "/ usr/lib64/python2.7/os.py", line 157, in makedirs2017-04-05 147path 42.108 5603 TRACE oslo_messaging.rpc.dispatcher mkdir (name Mode) 2017-04-05 1415 07VR 42.108 5603 TRACE oslo_messaging.rpc.dispatcher OSError: [Errno 13] Permission denied:'/ var/lock/cinder'

After the openstack-cinder-volume node machine restarts, the / var/lock/cinder directory is deleted automatically, and you need to create it manually after booting (where you met before, for a long time, it was a bit forgotten, except for errors, you still have to check the log the first time. Don't take it for granted)

# cd / var/lock # mkdir cinder# chown cinder:cinder cinder/# cd cinder/# lscinder-ea1f5135-3489-4d8e-99ab-8d2df0e06ff4-delete_volume

If you delete it again, you will see that there will be a temporary space-time file under the new directory that deletes the volume.

The above is all the contents of the article "what to do when the cloud disk is in deleting all the time". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.