@Bert
I think the problem you saw was due to a race I think I've now fixed, where the hostname for the lead unit is not present in /etc/hosts at the point where the third unit tried to cluster.
Pushed updates to:
cs:~james-page/xenial/rabbitmq-server-bug1584902
Please re-test!
@Bert
I think the problem you saw was due to a race I think I've now fixed, where the hostname for the lead unit is not present in /etc/hosts at the point where the third unit tried to cluster.
Pushed updates to:
cs:~james- page/xenial/ rabbitmq- server-bug1584902
Please re-test!