It looks like when designate is initially installed (maybe just the packages from an install hook ?) it comes up on port 9001. Then the hacluster charm is introduced and haproxy cannot start because it is also trying to bind to 9001. Then designate renders its config and switches to listening on 8991, but by this time haproxy (or crm/systemd) has given up on the service and it remains down. Before my environment disappeared I was able to gather the following:
Designate api log:
2019-10-01 10:38:06.858 15761 INFO designate.utils [-] Opening TCP Listening Socket on 0.0.0.0:9001
syslog:
Oct 1 11:34:31 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25726]: [ALERT] 273/113431 (25730) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [0.0.0.0:9001]
Oct 1 11:34:31 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25726]: [ALERT] 273/113431 (25730) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [:::9001]
Oct 1 11:34:32 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25749]: [ALERT] 273/113432 (25752) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [0.0.0.0:9001]
Oct 1 11:34:32 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25749]: [ALERT] 273/113432 (25752) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [:::9001]
Oct 1 11:34:32 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25766]: [ALERT] 273/113432 (25772) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [0.0.0.0:9001]
Oct 1 11:34:32 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25766]: [ALERT] 273/113432 (25772) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [:::9001]
Oct 1 11:34:32 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25790]: [ALERT] 273/113432 (25793) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [0.0.0.0:9001]
Oct 1 11:34:32 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25790]: [ALERT] 273/113432 (25793) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [:::9001]
Oct 1 11:34:33 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25810]: [ALERT] 273/113433 (25813) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [0.0.0.0:9001]
Oct 1 11:34:33 juju-496610-auto-osci-sv13-15 haproxy-systemd-wrapper[25810]: [ALERT] 273/113433 (25813) : Starting frontend tcp-in_designate-api_admin: cannot listen to socket [:::9001]
Oct 1 11:34:33 juju-496610-auto-osci-sv13-15 crmd[31177]: notice: juju-496610-auto-osci-sv13-15-res_designate_haproxy_start_0:39 [ Job for haproxy.service failed. See "systemctl status haproxy.service" and "journalctl -xe" for details.\n ]
designate-api log:
2019-10-01 11:36:44.367 25929 INFO designate.utils [-] Opening TCP Listening Socket on 0.0.0.0:8991
