From ed981ce09ad7ea5dd82c7b620abe9ecce2c1d797 Mon Sep 17 00:00:00 2001
From: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
Date: Tue, 27 Feb 2024 19:46:08 +0100
Subject: [PATCH] Use correct permissions for haproxy log mount

With [1] a regression was introduced, where incorrect permissions were
applied to a bind mount corrupting access to /dev/log globally on hosts
where haproxy was running.

Default permissions are 0666 for /dev/log when it's managed by journald.

[1] https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/888143
Closes-Bug: #2055178

Change-Id: Ib8b9e4dea0ecd5d35f0e872dfaa0f2ec837a98f8
---
 tasks/haproxy_post_install.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tasks/haproxy_post_install.yml b/tasks/haproxy_post_install.yml
index d558e84..b8b1d4b 100644
--- a/tasks/haproxy_post_install.yml
+++ b/tasks/haproxy_post_install.yml
@@ -77,7 +77,7 @@
     path: "{{ haproxy_log_mount_point }}"
     access_time: preserve
     modification_time: preserve
-    mode: "0755"
+    mode: "0666"
 
 - name: Make log socket available to chrooted filesystem
   mount: