RabbitMQ cluster fault after pacemeker OCF parameter changed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirantis OpenStack |
New
|
High
|
Unassigned | ||
6.1.x |
New
|
Critical
|
Unassigned |
Bug Description
After update OCF parameters of rabbitmq cluster by command "crm configure edit p_rabbitmq-server"
from:
params node_port=5673 debug=false command_
to:
params node_port=5673 debug=false command_
Slaves of rabbitmq cluster has been shutdown by pacemaker and newer get up.
How to reproduce:
1. install environment with HA mode (3 controllers)
2. start rabbitmq service by pacemaker.
3. make sure that cluster in proper state: command "rabbitmqctl cluster_status" shows 3 nodes in cluster
root@node-1:~# rabbitmqctl cluster_status
Cluster status of node 'rabbit@node-1' ...
[{nodes,
{running_
{cluster_
{partitions,[]}]
...done.
4. run "crm configure edit p_rabbitmq-server" on controller
5. change any value.
6. save config and exit from editor
7. in a minute check rabbbitmq cluster status using "rabbitmqctl cluster_status"
root@node-1:~# rabbitmqctl cluster_status
Cluster status of node 'rabbit@node-1' ...
[{nodes,
{running_
{cluster_
{partitions,[]}]
...done.
8. in a 2 minutes check rabbitmq cluster status by command: pcs status
Master/Slave Set: master_
p_
p_
and then
Master/Slave Set: master_
Masters: [ node-1.domain.local ]
Stopped: [ node-2.domain.local node-3.domain.local ]
after restart
Master/Slave Set: master_
Masters: [ node-1.domain.local ]
Slaves: [ node-2.domain.local node-3.domain.local ]
root@node-1:~# rabbitmqctl cluster_status
Cluster status of node 'rabbit@node-1' ...
[{nodes,
{running_
{cluster_
{partitions,[]}]
tags: | added: customer-found support |
Changed in mos: | |
importance: | Undecided → High |
no longer affects: | mos/7.0.x |