** 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:
Confirmed with Drew that this bug has not been hit since the pacemaker
fix released.
Can remove field-high team, but keep for the discussion on init-system-
helpers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
>From a high level, it appears that invoke-rc.d script used for
compatibility falls back to checking for /etc/rcX.d symlinks for a
"policy" check if there is no $POLICYHELPER installed. Perhaps the
actual shortcoming is not having the policy-rc.d installed to prefer
systemd over init.d on Xenial.
Is systemd's sysv-generator prioritized over regular systemd unit files
? My question raises from this fix. It looks like unit files were
automatically created because of the existence of the wrong LSB
parameters in init files - by the generator - but at the same time
Xenial should be using
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu Zesty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu Artful)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: init-system-helpers (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
re: init-system-helpers, I noticed the oddity of the init script on a
systemd system as well and found that there's a systemd hack in /lib/lsb
/init-functions.d/40-systemd that allows for multi-startup
compatibility. I believe invoke-rc.d should check systemd
"enabled/disabled" state instead of
** Tags added: uosci
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1727063
Title:
Pacemaker package upgrades stop but fail to start pacemaker resulting
in
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1727063
Title:
Pacemaker package upgrades stop but fail to start pacemaker resulting
in
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):
-
Did some touch testing in a VM and confirmed that the 1.2 package loses
its daemons on any kind of reconfigured. This behaviour is rectified
with the 1.3 package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Also validated that the update fixes an existing machine with the 1.2
update on it (with pacemaker services not running).
Pacemaker started after the update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Tested proposed package upgrade and works for me -
http://pastebin.ubuntu.com/25815820/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1727063
Title:
Testing from security-proposed PPA:
Broken install (dpkg-reconfigure pacemaker already run, daemons
stopped): Packages updated and pacemaker daemon restarted by postinst:
OK
Running install (pacemaker daemons running prior to pkg upgrade):
Packages update, pacemaker daemon stop prior to unpack
Also tested proposed fix on a three unit gnocchi HA deployment; all
pacemaker updates applied and restarted pacemaker postinst as desired.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
Updates building in:
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to init-system-helpers in
Ubuntu.
https://bugs.launchpad.net/bugs/1727063
Title:
** Description changed:
[Impact]
upgrades of the pacemaker package don't restart pacemaker after the package
upgrade, resulting in down HA clusters.
[Test Case]
sudo apt install pacemaker
sudo systemctl start pacemaker
sudo dpkg-reconfigure pacemaker
pacemaker daemons will
Tested OK (pacemaker was restarted after upgrade)
Uploaded to unapproved queue for SRU Team review - I'd suggest we
fasttrack this ASAP into -updates and -security to catch auto updates
for those systems not already updated.
--
You received this bug notification because you are a member of
Doing some testing via:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3010
before upload to xenial-proposed; not that the act of fixing this
problem will in itself cause the pacemaker daemons to be started on
upgrade. However it won't be auto-applied on a default install (unlike
Proposed update for xenial
** Patch added: "pacemaker.debdiff"
https://bugs.launchpad.net/ubuntu/zesty/+source/pacemaker/+bug/1727063/+attachment/4993845/+files/pacemaker.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
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
24 matches
Mail list logo
