14 Nov
2020
14 Nov
'20
2:10 a.m.
Hello,
What we noticed in our case is that nova compute is actually reconnecting, but cannot communicate with the conductor because the queue binding is either absent or not working anymore.
So, first, which version of nova are you running? Which version of rabbitmq? (some bugs related to shadow bindings are fixed after 3.7.x / dont remember x)
Can you check if you have any queue related to your compute? something like that: rabbtitmqctl list_queues | grep mycompute
Also check the bindings, better using the management interface or rabbitmqadmin: rabbitmqadmin list bindings | grep mycompute
What usually fixed our issue by the past was to delete / recreate the binding (easy to do from the management interface).
Cheers,
--
Arnaud Morin
On 14.11.20 - 00:34, Tony Liu wrote:
> Hi,
>
> I'm having a deployment with Ussuri on CentOS 8.
> I noticed that, in case the connection from nova-compute to
> rabbitmq is broken, nova-compute doesn't reconnect.
> I checked nova-conductor who seems keeping trying reconnect
> to rabbitmq when connection is broken. But nova-compute
> doesn't seem doing the same. I've seen it a few times, after
> I fixed rabbitmq and bring it back, nova-conductor gets
> reconnected, but nova-compute doesn't, I have to manually
> restart it. Anyone else has the similar experiences?
> Anything I am missing?
>
>
> Thanks!
> Tony
>
>