Comment 5 for bug 2055178

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-ansible-haproxy_server (stable/2023.2)

Reviewed: https://review.opendev.org/c/openstack/openstack-ansible-haproxy_server/+/911603
Committed: https://opendev.org/openstack/openstack-ansible-haproxy_server/commit/399a1d50b5f2d4e1f8783427eb0503eef48d789a
Submitter: "Zuul (22348)"
Branch: stable/2023.2

commit 399a1d50b5f2d4e1f8783427eb0503eef48d789a
Author: Dmitriy Rabotyagov <email address hidden>
Date: Tue Feb 27 19:46:08 2024 +0100

    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
    (cherry picked from commit ed981ce09ad7ea5dd82c7b620abe9ecce2c1d797)