You are forcing the compatibility between sysv and systemd into a corner here. I understand that your idea is to provide a simple case to reproduce the bug, but let's step back for a second and look at this statement:
""" The initscript is used as a LSB RA for pacemaker deployments; this bug effectively prevents pacemaker from realizing that haproxy is down (in some cases). """ The above is the original reason for this bug. Is masking the service via systemd one of those cases? As you saw in /lib/lsb/init- functions.d/40-systemd, the 0 exit status is quite explicit for masked services, and not something we should change lightly. Another option, I'm guessing, would be to change pacemaker to use systemctl instead of the initscript directly. No idea how feasible that is. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1810926 Title: initscript status check is too fragile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1810926/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
