[TestImpact][system-tests] Test change pacemaker parameter does not break RabbitMQ

[Dmitry Mescheryakov]

The test is intended to catch the bug https://bugs.launchpad.net/fuel/+bug/1496386

TestCase:
1. Deploy an environment with at least 3 controllers
2. On one of the controllers execute the following command:
crm_resource --resource p_rabbitmq-server --set-parameter max_rabbitmqctl_timeouts --parameter-value 5

All slave instances of RabbitMQ will be restarted shortly after that by Pacemaker

3. Wait for 1 minute.
4. Start checking that RabbitMQ cluster is assembled until success (see the procedure below). Fail test if cluster is not assembled in 10 (15?) minutes.

Procedure to check that cluster is assembled:
On each controller execute 'rabbitmqctl cluster_status' the output must list all controllers in 'running_nodes' list.
Also on each controller execute 'rabbitmqctl list_queues'. Check that command returned with 0.

Declare RabbitMQ cluster assembled if the procedure succeeds three times in a row.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/238465

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/238465
Committed: https://git.openstack.org/cgit/openstack/fuel-qa/commit/?id=dde73b2d9ebff4de8b98b8189786bc2d12ce68d7
Submitter: Jenkins
Branch: master

commit dde73b2d9ebff4de8b98b8189786bc2d12ce68d7
Author: vgorin <email address hidden>
Date: Thu Oct 22 14:37:32 2015 +0300

    Add test change pacemaker parameter does not break RabbitMQ

    Closes-Bug: #1498160
    Change-Id: I7b62db419c34e83d3faa46dccc8f6d44bf4e16e4