← Back to team overview

sts-sponsors team mailing list archive

[Bug 1819046] [NEW] Systemd unit file reads settings from wrong path

 

You have been subscribed to a public bug by Heitor R. Alves de Siqueira (halves):

[Impact]
Systemd Unit file doesn't read any settings by default

[Description]
The unit file shipped with the Xenial pacemaker package tries to read environment settings from /etc/sysconfig/ instead of /etc/default/. The result is that settings defined in /etc/default/pacemaker are not effective.
Since the /etc/default/pacemaker file is created with default values when the pacemaker package is installed, we should source that in the systemd unit file.

[Test Case]
1) Deploy a Xenial container:
    $ lxc launch ubuntu:xenial pacemaker
2) Update container and install pacemaker:
    root@pacemaker:~# apt update && apt install pacemaker -y
3) Check the systemd unit file for the "EnvironmentFile" option:
    root@pacemaker:~# systemctl cat pacemaker | grep EnvironmentFile
    EnvironmentFile=-/etc/sysconfig/pacemaker
    EnvironmentFile=-/etc/sysconfig/sbd

[Regression Potential]
The regression potential for this should be very low, since the configuration file is already being created by default and other systemd unit files are using the /etc/default config. In case the file doesn't exist or the user removed it, the "-" prefix will gracefully ignore the missing file according to the systemd.exec manual [0].
Nonetheless, the new package will be tested with autopkgtests and the fix will be validated in a reproduction environment.

[0] https://www.freedesktop.org/software/systemd/man/systemd.exec.html

** Affects: pacemaker (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: pacemaker (Ubuntu Xenial)
     Importance: Undecided
     Assignee: Heitor R. Alves de Siqueira (halves)
         Status: Confirmed


** Tags: sts sts-sponsor
-- 
Systemd unit file reads settings from wrong path
https://bugs.launchpad.net/bugs/1819046
You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.