resource-agents regression causes rabbitmq-bundle failures after certain resource restarts

Solution Verified - Updated -

Issue

A regression was introduced in resource-agents-4.1.1-12.el7_6.6.x86_64.rpm. It doesn't allow rabbitmq-bundle to become active after simultaneous reboot of controller nodes bug #1656733 and causes rabbit failures after OCF restarts inside the rabbitmq-bundle bug #1657138.

In one environment rabbitmq-bundle resource was active, but rabbitmq server wasn't stable and sporadically dropped inbound connections:


=ERROR REPORT==== 6-Mar-2019::10:02:04 === closing AMQP connection <0.21417.2> (192.168.12.12:43886 -> 192.168.12.12:5672 - neutron-server:52:c45f2bdd-4666-46a8-806c-823edbfe7cef): missed heartbeats from client, timeout: 60s =INFO REPORT==== 6-Mar-2019::10:02:05 === accepting AMQP connection <0.21838.2> (192.168.12.12:54242 -> 192.168.12.12:5672) =INFO REPORT==== 6-Mar-2019::10:02:05 === Connection <0.21838.2> (192.168.12.12:54242 -> 192.168.12.12:5672) has a client-provided name: neutron-server:52:c45f2bdd-4666-46a8-806c-823edbfe7cef =INFO REPORT==== 6-Mar-2019::10:02:05 === connection <0.21838.2> (192.168.12.12:54242 -> 192.168.12.12:5672 - neutron-server:52:c45f2bdd-4666-46a8-806c-823edbfe7cef): user 'guest' authenticated and granted access to vhost '/'

Environment

  • Red Hat OpenStack Platform 10
  • Red Hat OpenStack Platform 13
  • Red Hat OpenStack Platform 14

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In