Some strange thing happens in Pacemaker: according to 'pcs status', both node-2 and node-5 are online and in the cluster: http://paste.openstack.org/show/479577/
At the same time lrmd.log for node-2 shows that LRMD daemon calls 'monitor' operation and it returns OCF_ERR_GENERIC. But pacemaker just ignores that. Also, lrmd.log for node-5 shows that OCF script constantly tries to join RabbitMQ on node-5 to the one on node-2, but fails since RabbitMQ on node-2 is stuck.
Still, the main problem here is that Pacemaker does not act on node-2, though OCF script returns OCF_ERR_GENERIC meaning there are problems here.
Some strange thing happens in Pacemaker: according to 'pcs status', both node-2 and node-5 are online and in the cluster: http:// paste.openstack .org/show/ 479577/
But 'pcs resource' does not show RabbitMQ status for node-2. Only node-5 is listed as slave: http:// paste.openstack .org/show/ 479576/
At the same time lrmd.log for node-2 shows that LRMD daemon calls 'monitor' operation and it returns OCF_ERR_GENERIC. But pacemaker just ignores that. Also, lrmd.log for node-5 shows that OCF script constantly tries to join RabbitMQ on node-5 to the one on node-2, but fails since RabbitMQ on node-2 is stuck.
Still, the main problem here is that Pacemaker does not act on node-2, though OCF script returns OCF_ERR_GENERIC meaning there are problems here.