After reboot the control node rabbitmq services not getting up.

Solution In Progress - Updated -

Issue

  • After reboot the control node rabbitmq services not geeting up.

  • We see the following in pcs status:

        Apr 14 17:27:50 overcloud-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 overcloud-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 overcloud-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 overcloud-controller-1 pacemaker-schedulerd[5585]: notice:  * Start      rabbitmq:2 (rabbitmq-bundle-2 )
          due to unrunnable rabbitmq-bundle-2 start (blocked)
  • There're no banned or disabled resources.

Environment

  • Red Hat OpenStack Platform 16.2 (RHOSP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content