Comment 2 for bug 1519366

I've looked at how RabbitMQ started on node-5. Here are excerpts from 10.109.0.2/var/log/docker-logs/remote/node-5.test.domain.local/lrmd.log from the snapshot: http://paste.openstack.org/show/479961/

In general, yes, joining cluster timed out on 1st attempt and so RabbitMQ was restarted. It successfully joined the cluster on the 2nd attempt. And anyway, all that took 5 minutes (instead of 2 minutes) and did not cause unrecoverable errors in puppet (please correct me if I am wrong).

So, to sum up, it looks like rabbitmq was not the cause of the job time out.