I've recently been exploring this same issue. This behaviour is caused by a bug in oslo.messaging, there's currently a couple of patches ongoing to resolve it:
In the meantime, I've found that setting the config option `[oslo_messaging_rabbit] kombu_reconnect_delay = 0.1` fixes this bug. This should be set for all services which use RabbitMQ.
These bug reports are relevant to see the oslo.messaging patch that caused the issue, and discussion on how it is being resolved:
Hi,
I've recently been exploring this same issue. This behaviour is caused by a bug in oslo.messaging, there's currently a couple of patches ongoing to resolve it:
https:/ /review. opendev. org/c/openstack /oslo.messaging /+/866616 /review. opendev. org/c/openstack /oslo.messaging /+/866617
https:/
In the meantime, I've found that setting the config option `[oslo_ messaging_ rabbit] kombu_reconnect _delay = 0.1` fixes this bug. This should be set for all services which use RabbitMQ.
These bug reports are relevant to see the oslo.messaging patch that caused the issue, and discussion on how it is being resolved:
https:/ /bugs.launchpad .net/cloud- archive/ +bug/1993149 /bugs.launchpad .net/kolla- ansible/ +bug/1990257
https:/