cause #2 (haproxy) it's actually a bug in haproxy code itself. Haproxy logs show
Oct 18 09:25:28 tripleo-centos-7-tripleo-test-cloud-rh1-4970270 haproxy-systemd-wrapper[29397]: [ALERT] 291/062528 (29398) : Starting proxy ceilometer: cannot bind socket [192.0.2.3:8777] Oct 18 09:25:28 tripleo-centos-7-tripleo-test-cloud-rh1-4970270 haproxy-systemd-wrapper[29397]: haproxy-systemd-wrapper: exit, haproxy RC=256
A RC of 256 is actually cut down to 0 in exit code standard (only least significant 8 bits of the exit code are actually used) So the wrapper returns as if it succeded.
cause #2 (haproxy) it's actually a bug in haproxy code itself. Haproxy logs show
Oct 18 09:25:28 tripleo- centos- 7-tripleo- test-cloud- rh1-4970270 haproxy- systemd- wrapper[ 29397]: [ALERT] 291/062528 (29398) : Starting proxy ceilometer: cannot bind socket [192.0.2.3:8777] centos- 7-tripleo- test-cloud- rh1-4970270 haproxy- systemd- wrapper[ 29397]: haproxy- systemd- wrapper: exit, haproxy RC=256
Oct 18 09:25:28 tripleo-
A RC of 256 is actually cut down to 0 in exit code standard (only least significant 8 bits of the exit code are actually used) So the wrapper returns as if it succeded.