After changing pacemaker parameter rabbit master node does not leave cluster
Bug #1618909 reported by
ElenaRossokhina
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Dmitry Mescheryakov | ||
Mitaka |
Fix Released
|
High
|
Dmitry Mescheryakov |
Bug Description
Detailed bug description:
According to logs, rabbit master node does not reboot and always stays in cluster after command to change max_rabbitmqctl
Parameter changed correctly.
Steps to reproduce:
https:/
Expected results:
test passed
Actual result:
system test failed: All nodes are staying in the cluster
Reproducibility:
on swarm, since 9.1 snapshot #169
logs https:/
tags: | added: area-library |
Changed in fuel: | |
importance: | Undecided → High |
status: | New → Confirmed |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
milestone: | none → 10.0 |
Changed in fuel: | |
status: | Confirmed → Invalid |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Dmitry Mescheryakov (dmitrymex) |
tags: | added: non-release |
tags: | added: rabbitmq |
To post a comment you must log in.
Hot fail: /product- ci.infra. mirantis. net/job/ 9.x.system_ test.ubuntu. ha_neutron_ destructive/ 52/testReport/ (root)/ change_ pacemaker_ parameter_ not_break_ rabbitmq/ change_ pacemaker_ parameter_ not_break_ rabbitmq/
https:/