[Starlingx-discuss] Openstack applying failed and nova-compute-worker-0 pod with CrashLoopBackOff staus

open infra openinfradn at gmail.com
Tue Jul 27 16:59:35 UTC 2021


Tried to start VMs using the hypervisor but no luck.

worker-0:~# virsh start instance-00000005
error: Failed to start domain instance-00000005
error: Secret not found: no secret with matching uuid
'457eb676-33da-42ec-9a8c-9293d545c337'

worker-0:~# virsh start instance-00000052
error: Failed to start domain instance-00000052
error: Secret not found: no secret with matching uuid
'457eb676-33da-42ec-9a8c-9293d545c337'

Could not figure what object is having the uuid of
457eb676-33da-42ec-9a8c-9293d545c337.


On Mon, Jul 26, 2021 at 6:28 PM open infra <openinfradn at gmail.com> wrote:

> Hi,
>
> After rebooting the entire stx (r5 standard dedicated storage)
> environment, noticed that OpenStack vm can not start and hypervisor status
> is down (we have only one worker node).
>
> Furthermore, openstack-apply was failed as
> nova-compute-worker-0-13cc482d-7t9kq pod was not ready [1] and status is
> CrashLoopBackOff [2]. Here is the description of the pod [3].
>
>
> VMs were created using nova-local and mounted a shared volume, which is a
> ceph based volume. Lock and Unlocking + re-applying of stx-openstack didn't
> fix the issue.
>
> I would like to know any hint or suggestion to fix this issue and avoid
> similar issue in future.
>
> [1] https://paste.opendev.org/show/807707/
> [2] https://paste.opendev.org/show/807705/
> [3] https://paste.opendev.org/show/807704/
>
> Regards,
> Danishka
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20210727/1b1cbb62/attachment.html>


More information about the Starlingx-discuss mailing list