Comment 44 for bug 1285449

After shutting down RabbitMQ on all controllers, upgrading to 3.2.4, and starting it back on one controller (last one to have been stopped, node-22), queues from all nodes are mastered on node-22:

cert <'rabbit@node-22'.1.763.0>
cert.node-20 <'rabbit@node-22'.1.764.0>
cert.node-21 <'rabbit@node-22'.1.915.0>
cert.node-22 <'rabbit@node-22'.1.943.0>
cert_fanout_41cd75baf6de4142ae27ac43d3fe1dd3 <'rabbit@node-22'.1.918.0>
cert_fanout_6e611b8e54ff40e6893f24f0f948da90 <'rabbit@node-22'.1.765.0>
cert_fanout_cad666b18f2d4283b0c9c059dd07f441 <'rabbit@node-22'.1.957.0>
cinder-scheduler <'rabbit@node-22'.1.1018.0>
cinder-scheduler:node-20 <'rabbit@node-22'.1.1024.0>
cinder-scheduler_fanout_e71b120de586417ab457d25e77414fbb <'rabbit@node-22'.1.1026.0>
cinder-volume <'rabbit@node-22'.1.1023.0>
cinder-volume:node-20 <'rabbit@node-22'.1.1025.0>
cinder-volume_fanout_60c40388ef08422f8ceea258e98f5134 <'rabbit@node-22'.1.1027.0>
compute <'rabbit@node-22'.1.1474.0>
compute.node-23 <'rabbit@node-22'.1.1476.0>
compute_fanout_bd7d38999ec6477cb5f0a411684c3bd9 <'rabbit@node-22'.1.1478.0>
...