Use KillMode=mixed in systemd service file to avoid incorrect exist code when stopping haproxy service.
sudo dnf upgrade --refresh --advisory=FEDORA-2017-a1468ad1ae
This update has been submitted for testing by rohara.
This update has been pushed to testing.
With this update I'm unable to start haproxy via systemd, see bug #1447800 Running the service from command line seems to work
# /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -Ds
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes
OK. I went back and tested the older haproxy build (haproxy-1.7.3-1.fc26.x86_64) and it also fails to start due to SELinux AVC, so this bug is not caused by this update.
This update has been submitted for stable by rohara.
This update has been pushed to stable.
#1447800 is still a thing
Please login to add feedback.
Confirm request to re-trigger tests.
This update has been submitted for testing by rohara.
This update has been pushed to testing.
With this update I'm unable to start haproxy via systemd, see bug #1447800 Running the service from command line seems to work
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has reached 3 days in testing and can be pushed to stable now if the maintainer wishes
OK. I went back and tested the older haproxy build (haproxy-1.7.3-1.fc26.x86_64) and it also fails to start due to SELinux AVC, so this bug is not caused by this update.
This update has been submitted for stable by rohara.
This update has been pushed to stable.
#1447800 is still a thing