SM: rabbitmq clustering fails
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.2 |
Fix Committed
|
Critical
|
Dheeraj Gautam | |||
R4.0 |
Fix Committed
|
Critical
|
Dheeraj Gautam | |||
Trunk |
Fix Committed
|
Critical
|
Dheeraj Gautam |
Bug Description
server1:
=WARNING REPORT==== 2-Jun-2017:
Could not auto-cluster with rabbit@server3ctrl: {badrpc,nodedown}
=WARNING REPORT==== 2-Jun-2017:
Could not auto-cluster with rabbit@server2ctrl: {error,
server2:
=WARNING REPORT==== 2-Jun-2017:
Could not auto-cluster with rabbit@server1ctrl: {error,
=WARNING REPORT==== 2-Jun-2017:
Could not auto-cluster with rabbit@server3ctrl: {badrpc,nodedown}
server3:
=INFO REPORT==== 2-Jun-2017:
Node 'rabbit@
Both server1 and server2 are coming up at the same time hence rabbitmq clustering failed.
This seems to be a known issue with rabbitmq and the WA is to start rabbitmq-service on one node first, wait for it to be fully-up, then start rabbitmq on all the other nodes (the service can be started on other nodes in parallel too).
tags: | added: blocker |
build number?