** No longer affects: init-system-helpers (Ubuntu Bionic)
** No longer affects: init-system-helpers (Ubuntu Artful)
** No longer affects: init-system-helpers (Ubuntu Zesty)
** No longer affects: init-system-helpers (Ubuntu Xenial)
** Changed in: init-system-helpers (Ubuntu)
Status:
This bug was fixed in the package pacemaker - 1.1.14-2ubuntu1.3
---
pacemaker (1.1.14-2ubuntu1.3) xenial; urgency=medium
* Fix default start/stop levels for init scripts, ensuring that
running pacemaker daemons are restarted after package upgrades
(LP: #1727063):
-
Actually this only impacts Xenial; Debian carried a patch from:
pacemaker (1.1.15~rc3-1) unstable; urgency=medium
[ Christoph Berg ]
* [23ee108] libcrmservice3.symbols: Exclude systemd symbol on non-linux
* [41dea05] Fix time formatting on x32
* [533c5cc] Fix FTBFS on GNU Hurd
[
This issue can be fixed by re-adding the required Start/Stop bits to the
LSB header; however the behaviour of update-rc.d when native systemd
unit files are in use looks odd to me.
Raising an init-system-helpers bug task for foundations team input on
this.
** Also affects: init-system-helpers
I think this is a packaging/upstream bug which I appear to have had a go
at before (see #4); however I've not seen this specific symptom before.
** Changed in: charm-hacluster
Status: New => Invalid
--
You received this bug notification because you are a member of नेपाली
भाषा
5 matches
Mail list logo
