[TestImpact][system-tests] Test change pacemaker parameter does not break RabbitMQ
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Vasily Gorin |
Bug Description
The test is intended to catch the bug https:/
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
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.
Changed in fuel: | |
milestone: | none → 8.0 |
importance: | Undecided → High |
status: | New → Confirmed |
assignee: | nobody → Fuel QA Team (fuel-qa) |
tags: | added: system-tests |
Changed in fuel: | |
assignee: | Fuel QA Team (fuel-qa) → Vasily Gorin (vgorin) |
tags: | added: area-qa |
Changed in fuel: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/238465
Review: https:/