Add a matrix of two test cases:
* Smoke test: just a check if rabbit cluster assembles.
* Jepsen test: allowed to fail, it's main value is to
verify cluster auto-healing after consequent network
partitions and to provide numbers for
duplicated/lost/recovered/unexpected messages as well.
Make the gate always passing if there is no changes found
to the RabbitMQ OCF RA script in the patch under test.
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
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
Partitions reported by `rabbit_node_monitor:partitions/0` are not
commutative (i.e. node1 can report itself as partitioned with node2, but
not vice versa).
Given that we now have strong notion of master in OCF script, we can
check for those fishy situations during master health check, and order
damaged nodes to restart.
Fuel bug: https://bugs.launchpad.net/fuel/+bug/1628487
Bogdan Dobrelya
Jean-Sébastien Pédron
Daniil Fedotov
Dmitry Mescheryakov
Alexey Lebedeff
Jean-Sébastien Pédron