Comment 6 for bug 1264388

Compared against a successful deployment with https://review.openstack.org/61940 reverted, the difference in the logs starts with:

2013-12-26T21:47:37.256453+00:00 notice: (/Stage[main]/Openstack::Controller_ha/Exec[restart_haproxy]/returns) [ALERT] 359/214735 (28437) : Starting proxy ceilometer: cannot bind socket
2013-12-26T21:47:37.257114+00:00 notice: (/Stage[main]/Openstack::Controller_ha/Exec[restart_haproxy]/returns) [ALERT] 359/214735 (28437) : Starting proxy ceilometer: cannot bind socket

The above seems to be the reason why haproxy failed to restart. netstat output from node-1 in the failed deployment contains the following:

tcp 0 0 0.0.0.0:8777 0.0.0.0:* LISTEN 20325/python

Compared to netstat from a successful deployment:

tcp 0 0 192.168.0.2:8777 0.0.0.0:* LISTEN 16730/haproxy
tcp 0 0 10.108.1.3:8777 0.0.0.0:* LISTEN 16730/haproxy
tcp 0 0 192.168.0.3:8777 0.0.0.0:* LISTEN 15417/python