My team recently ran into a bizarre RMQ partition failure in a production cluster. RMQ doesn't handle partition failures well, and while you can set up auto recovery (such as suspension of minority groups) you need to manually recover from it. The one time I've encountered this I got a very useful message in the admin managment page indicating that parts of the cluster were in partition failure, but this time things went weird.
In the end the solution was to do an NTP time sync, turn off all clustered slaves (shut down their VM's, not go into suspension). Once that occurred, the master was rebooted and then it stabilized. After that we brought up each slave one by one until it went green.
Anyways, figured I'd share the symptoms and the solution in case anyone else runs into it.