When haproxy is restarted the original process remains leaving multiple haproxies running

[David Ames]

While testing https://code.launchpad.net/~jjo/charms/trusty/nova-cloud-controller/fix-haproxy-cfg-for-neutron-api-lp1476394/+merge/265341 I discovered that when haproxy is restarted (stopped/started) the process is not getting killed. This leaves multiple haproxies running:

root@juju-thedac-machine-5:# ps -ef |grep haproxy
haproxy 10061 1 0 14:53 ? 00:00:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid
haproxy 27031 1 0 15:06 ? 00:00:00 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p /var/run/haproxy.pid

root@juju-thedac-machine-5:# netstat -tlnp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1051/sshd
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 27031/haproxy
tcp 0 0 0.0.0.0:8888 0.0.0.0:* LISTEN 10061/haproxy
tcp 0 0 0.0.0.0:8763 0.0.0.0:* LISTEN 13761/python
tcp 0 0 0.0.0.0:3323 0.0.0.0:* LISTEN 13808/python
tcp 0 0 0.0.0.0:8764 0.0.0.0:* LISTEN 13782/python
tcp 0 0 0.0.0.0:9696 0.0.0.0:* LISTEN 10061/haproxy
tcp 0 0 0.0.0.0:3333 0.0.0.0:* LISTEN 27031/haproxy
tcp 0 0 0.0.0.0:8773 0.0.0.0:* LISTEN 27031/haproxy
tcp 0 0 0.0.0.0:3333 0.0.0.0:* LISTEN 10061/haproxy
tcp 0 0 0.0.0.0:8773 0.0.0.0:* LISTEN 10061/haproxy
tcp 0 0 0.0.0.0:8774 0.0.0.0:* LISTEN 27031/haproxy
tcp 0 0 0.0.0.0:8774 0.0.0.0:* LISTEN 10061/haproxy
tcp6 0 0 :::22 :::* LISTEN 1051/sshd
tcp6 0 0 :::80 :::* LISTEN 7327/apache2

[Nobuto Murata (nobuto)]

It sounds like bug #1477198 (SRU in progress).

[David Ames (thedac)]

JuanJo Ciarlante confirms this bug is present in multiple Openstack charms that use haproxy.

Confirmed the -proposed SRU from bug #1477198 resolves the problem