[library] RabbitMQ doesn't assemble after controller reboot

{"build_id": "2014-07-18_22-06-01", "ostf_sha": "9863db951a6e159f4fa6e6861c8331e1af069cf8", "build_number": "333", "auth_required": false, "api": "1.0", "nailgun_sha": "d7408251ec27dd65447ea2c0a96e5456697047c7", "production": "docker", "fuelmain_sha": "a379af4c5ca38fef7bf4d7b35abc45034a533791", "astute_sha": "9f1e69aa3a2fe7a6093fa50596d6931826d93a09", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "7d7ec0d76eb97689717b266151e98d813f0acb8d"}

Periodically when rebooting a controller only 2 of 3 controllers rejoin the cluster. After rebooting controller 2 only controllers 1 and 2 join the Rabbit cluster.

[root@node-1 ~]# rabbitmqctl cluster_status
Cluster status of node 'rabbit@node-1' ...
[{nodes,[{disc,['rabbit@node-1','rabbit@node-2','rabbit@node-3']}]},
 {running_nodes,['rabbit@node-2','rabbit@node-1']},
 {partitions,[]}]
...done.

[root@node-3 ~]# rabbitmqctl cluster_status
Cluster status of node 'rabbit@node-3' ...
[{nodes,[{disc,['rabbit@node-3']}]}]
...done.

node-3 doesn't join the cluster because the rabbit app is stopped.

[root@node-3 ~]# rabbitmqctl status
Status of node 'rabbit@node-3' ...
[{pid,31333},
 {running_applications,[{xmerl,"XML parser","1.2.10"},
                        {sasl,"SASL CXC 138 11","2.1.10"},
                        {stdlib,"ERTS CXC 138 10","1.17.5"},
                        {kernel,"ERTS CXC 138 10","2.14.5"}]},