From fb9f46cc4791f133c7b96d98c807f53cc9eab5a7 Mon Sep 17 00:00:00 2001 From: "Dustin C. Hatch" Date: Tue, 22 Jul 2025 09:55:00 -0500 Subject: [PATCH] r/haproxy: Do not start service Since the _haproxy_ role relies on other roles to provide drop-in configuration files for actual proxy configuration, we cannot start the service in the base role. If there are any issues with the drop-in files that are added later, the service will not be able to start, causing the playbook to fail and thus never be able to update the broken configuration. The dependent roles need to be responsible for starting the service once they have put their configuration files in place. --- roles/haproxy/tasks/main.yml | 7 ------- 1 file changed, 7 deletions(-) diff --git a/roles/haproxy/tasks/main.yml b/roles/haproxy/tasks/main.yml index 627ec9e..0a17d32 100644 --- a/roles/haproxy/tasks/main.yml +++ b/roles/haproxy/tasks/main.yml @@ -46,13 +46,6 @@ tags: - service -- name: ensure haproxy is running - service: - name: haproxy - state: started - tags: - - service - - name: ensure firewall is configured for haproxy stats firewalld: port: '{{ haproxy_stats_port }}/tcp'