After rebooting a controller node the `rabbitmq` services is not starting and we see the following in `pcs status`:
Issue
-
After rebooting a controller node the
rabbitmq
services is not starting and we see the following inpcs status
:Apr 14 17:27:50 controller-1 pacemaker-schedulerd[5585]: warning: Unexpected result (error) was recorded for start of rabbitmq:0 on rabbitmq-bundle-0 at Apr 14 16:58:39 2023 Apr 14 17:27:50 controller-1 pacemaker-schedulerd[5585]: warning: Unexpected result (error) was recorded for start of rabbitmq:2 on rabbitmq-bundle-2 at Apr 14 16:55:19 2023 Apr 14 17:27:50 controller-1 pacemaker-schedulerd[5585]: notice: * Start rabbitmq:0 (rabbitmq-bundle-0 ) due to unrunnable rabbitmq-bundle-0 start (blocked) Apr 14 17:27:50 controller-1 pacemaker-schedulerd[5585]: notice: * Start rabbitmq:2 (rabbitmq-bundle-2 ) due to unrunnable rabbitmq-bundle-2 start (blocked)
Environment
- Red Hat OpenStack Platform 16.2 (RHOSP)
- Red Hat Enterprise Linux Server 7, 8, 9 (with the High Availability Add On)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.