The question about OpenStack instance fail to boot after unexpected compute node shutdown

CHANU ROMAIN romain.chanu at univ-lyon1.fr
Sat Sep 26 12:48:24 UTC 2020


Hello,


You have to remove the ceph lock:


$1 = pool

$2 = volume name

    read -r -a vars <<< $(rbd -p $1 lock list $2  | tail -1)
    rbd -p  $1 lock remove $2 "${vars[1]} ${vars[2]}" ${vars[0]}

Best regards,


Romain


________________________________
From: Yule Sun <373056786 at qq.com>
Sent: Friday, September 25, 2020 5:47 AM
To: rony.khan at brilliant.com.bd; openstack-discuss at lists.openstack.org
Subject: The question about OpenStack instance fail to boot after unexpected compute node shutdown

I saw your message on the website http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005635.html . And  i have been troubled by the same problem for a long time . I tried to change the parameters resume_guests_state_on_host_boot=True and instance_usage_audit=True
in the nova.conf ,but it didn't work . I wonder if you have solved this problem, looking forward your reply, Thank you and best regards.

And my instance error looks like this .
[cid:e8770762-d2b2-4630-9ce6-4d357dc92cee]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200926/b41e77cb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2020-09-25_114323.png
Type: image/png
Size: 16879 bytes
Desc: 2020-09-25_114323.png
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200926/b41e77cb/attachment-0001.png>


More information about the openstack-discuss mailing list