Panicking and returning non-success on stop often leads to resource becoming unmanaged on that node. Before we called get_status to verify that RabbitMQ is dead. But sometimes it returns error even though RabbitMQ is not running. There is no reason to call it - we will just verify that there is no beam process running. Related fuel bug - https://bugs.launchpad.net/fuel/+bug/1626933 |
||
---|---|---|
.. | ||
rabbitmq-script-wrapper | ||
rabbitmq-server-ha.ocf | ||
rabbitmq-server.ocf | ||
travis_test_ocf_ra.sh |