Comment 7 for bug 1623882

The original problem in this issue is sequence of upgrading.
Because of fuel-ha-utils package upgraded - that brings new ocf code for rabbitmq. The status command was changed and is not compatible with 3.6.1 rabbit. After that pacemaker starts to think that rabbit is dead - because monitor command returns error and tries to restart cluster.

To properly fix this - either you should upgrade rabbitmq-server first and than fuel-ha-utils, or set OCF_RESKEY_rmq_feature_health_check == 'false', that will trigger node_health_check_legacy() function to do verification - that supports both version.