rabbitmq nodes repeatedly reporting the master node as being 'down' then 'up'

[Tom Howley]

I have a 3-node notcompute/control setup in my overcloud with a rabbitmq cluster across the three nodes:

notcompute0 is the master in the cluster.
The other two nodes are repeatedly logging messages, such as the following:

=INFO REPORT==== 17-Apr-2014::13:49:26 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

=INFO REPORT==== 17-Apr-2014::13:50:10 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' down

=INFO REPORT==== 17-Apr-2014::13:50:12 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

=INFO REPORT==== 17-Apr-2014::13:50:56 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' down

=INFO REPORT==== 17-Apr-2014::13:50:58 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

=INFO REPORT==== 17-Apr-2014::13:51:43 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' down

=INFO REPORT==== 17-Apr-2014::13:51:45 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

=INFO REPORT==== 17-Apr-2014::13:52:08 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' down

=INFO REPORT==== 17-Apr-2014::13:52:09 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

=INFO REPORT==== 17-Apr-2014::13:52:29 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' down

=INFO REPORT==== 17-Apr-2014::13:52:31 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

=INFO REPORT==== 17-Apr-2014::13:53:15 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' down

=INFO REPORT==== 17-Apr-2014::13:53:17 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

=INFO REPORT==== 17-Apr-2014::13:54:02 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' down

=INFO REPORT==== 17-Apr-2014::13:54:04 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

=INFO REPORT==== 17-Apr-2014::13:54:48 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' down

=INFO REPORT==== 17-Apr-2014::13:54:50 ===
rabbit on node 'rabbit@overcloud-notcompute0-nnu4kdtefome' up

[Robert Collins (lifeless)]

we don't have hostname propogation for multi-node control planes yet (amongst other issues) - so this is probably a symptom of multi-node control planes not being finished yet.

[Tom Howley (tom-howley)]

Just to clarify that hit this issue with a working rabbitmq cluster over three overcloud controller nodes.

[Ben Nemec (bnemec)]

Just setting an importance so this will stop showing up in the untriaged list. :-)

If this persists after the multi-node control planes are expected to be working then we need to revisit it.

[Launchpad Janitor (janitor)]

[Expired for tripleo because there has been no activity for 60 days.]