Hello Niels,
a restart means stopping haproxy - and after haproxy exited completely, starting haproxy again. When that happens, haproxy immediately stops listening to the sockets and then waits for existing connections to be closed (you can accelerate that with hard-stop-after [1], but that's not the point). So what you are seeing is expected behavior when RESTARTING. Seems to me you want RELOAD behavior instead, so RELOAD is what Ansible should trigger when it detects a config change, no RESTART. cheers, lukas [1] https://cbonte.github.io/haproxy-dconv/1.7/configuration.html#hard-stop-after
