Comment 8 for bug 1813900

Not sure the haproxy sigterm is an issue.
I'm pushing this change[1] in order to get ip6tables state, as it *might* be the issue since ipv6 is usually preferred over ipv6 for connections, i.e. ansible to localhost.
But even if ip6tables isn't OK (and I'm pretty sure it's OK), we should get a connection error from ansible.

IIRC, that step 2 thing is still host configuration, meaning "no container involved", "only puppet deploy on the host".... So that's pretty weird.

[1] https://review.openstack.org/#/c/633922/