Comment 0 for bug 1407678

Steps to reproduce:
1. Find management_vip node:
# ssh node-1 'crm status'
2. Reboot node with any other at the same time:
# for i in node-{1,2}; do ssh $i 'nohup reboot &'; done
3. In ~10% cases one node will hang on shutdown process.
3. In ~30% cases one nodes' shutdown process takes a lot of time

Looks like problem with RabbitMQ or RabbitMQ resource agent.
I tested reboot after disabling rabbitmq-server, 5/5 tries ends with success.

Setting shutdown-escalation="120" as cluster properties solves issue