False-positive monitoring result of rabbitmq resource when rabbitmq cluster is partitioned

Solution In Progress - Updated -


After network problem where pacemaker cluster became inquorate the network connection was re-established and pacemaker cluster become quorate at once and continued operation however rabbitmq cluster (running on top of pacemaker cluster) was partitioned in the meantime and resource-agent didn't react to that.


  • Red Hat OpenStack Platform 13
  • Pacemaker cluster
  • RabbitMQ cluster running on top of pacemaker cluster

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