Comment 19 for bug 1993149

I tried the package on PPA on Focal Yoga and it did solve the issue and deploying resources seems to work on my lab. So finding the culprit is done, thank you Corey for that + the PPA package.

Just in case, I made a test on Jammy Zed Openstack release. Although it uses a more recent version of python3-oslo.messaging, closer to upstream release, the issue is still present, although in a slightly less severe manner.
--> the units would still spam every seconds about trying to reconnect indefinitely to the RabbitMQ unit

this didn't happen when shutting down any RabbitMQ but only one or two specific units only among 3 of them.
--> I think it depends most likely on which rabbitmq server, the Nova/Cinder/Glance/Neutron workers have decided to connect to.
(Although this might be because aside from Mysql-innodb-cluster and rabbitmq-server, the control plane units are not in HA so there are way fewer units involved in my test)