Activity log for bug #1727063

Date Who What changed Old value New value Message
2017-10-24 20:50:46 Drew Freiberger bug added bug
2017-10-24 23:10:48 David Ames bug task added pacemaker (Ubuntu)
2017-10-24 23:19:30 David Ames charm-hacluster: importance Undecided Critical
2017-10-25 02:16:56 Takafumi Koyama bug added subscriber Takafumi Koyama
2017-10-25 02:17:12 Launchpad Janitor pacemaker (Ubuntu): status New Confirmed
2017-10-25 07:54:43 Dmitrii Shcherbakov tags canonical-bootstack canonical-is pacemaker sts canonical-bootstack canonical-is cpe-onsite pacemaker sts
2017-10-25 08:07:12 James Page pacemaker (Ubuntu): status Confirmed Triaged
2017-10-25 08:07:23 Dominique Poulain bug added subscriber Dominique Poulain
2017-10-25 08:10:44 James Page pacemaker (Ubuntu): importance Undecided High
2017-10-25 08:10:48 James Page pacemaker (Ubuntu): importance High Critical
2017-10-25 08:13:11 James Page nominated for series Ubuntu Artful
2017-10-25 08:13:11 James Page bug task added pacemaker (Ubuntu Artful)
2017-10-25 08:13:11 James Page nominated for series Ubuntu Xenial
2017-10-25 08:13:11 James Page bug task added pacemaker (Ubuntu Xenial)
2017-10-25 08:13:11 James Page nominated for series Ubuntu Bionic
2017-10-25 08:13:11 James Page bug task added pacemaker (Ubuntu Bionic)
2017-10-25 08:13:11 James Page nominated for series Ubuntu Zesty
2017-10-25 08:13:11 James Page bug task added pacemaker (Ubuntu Zesty)
2017-10-25 08:13:21 James Page pacemaker (Ubuntu Zesty): importance Undecided Critical
2017-10-25 08:13:23 James Page pacemaker (Ubuntu Artful): importance Undecided Critical
2017-10-25 08:13:27 James Page pacemaker (Ubuntu Xenial): status New Triaged
2017-10-25 08:13:33 James Page pacemaker (Ubuntu Zesty): status New Triaged
2017-10-25 08:17:22 James Page pacemaker (Ubuntu Xenial): importance Undecided Critical
2017-10-25 08:17:27 James Page pacemaker (Ubuntu Artful): status New Triaged
2017-10-25 08:21:58 James Page charm-hacluster: status New Invalid
2017-10-25 08:24:55 Dmitrii Shcherbakov bug added subscriber Dmitrii Shcherbakov
2017-10-25 08:37:35 John Lewis bug added subscriber John Lewis
2017-10-25 08:39:11 James Page description We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. [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 not be restarted. [Regression Potential] TBC as not quite sure where the fix for this is. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:.
2017-10-25 08:44:54 James Page bug task added init-system-helpers (Ubuntu)
2017-10-25 08:56:36 James Page pacemaker (Ubuntu Bionic): status Triaged Fix Released
2017-10-25 08:57:21 James Page pacemaker (Ubuntu Artful): status Triaged Fix Released
2017-10-25 08:57:41 James Page pacemaker (Ubuntu Zesty): status Triaged Fix Released
2017-10-25 09:05:30 James Page attachment added pacemaker.debdiff https://bugs.launchpad.net/ubuntu/zesty/+source/pacemaker/+bug/1727063/+attachment/4993845/+files/pacemaker.debdiff
2017-10-25 09:06:11 James Page bug added subscriber Ubuntu Stable Release Updates Team
2017-10-25 09:44:40 Sandor Zeestraten bug added subscriber Sandor Zeestraten
2017-10-25 10:04:27 James Page description [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 not be restarted. [Regression Potential] TBC as not quite sure where the fix for this is. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:. [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 not be restarted. [Regression Potential] Minimal, earlier and later versions provide the defaults in the lsb header. [Original Bug Report] We have found on our openstack charm-hacluster implementations that the pacemaker .deb packaging along with the upstream pacemaker configuration result in pacemaker stopping but not starting upon package upgrade (while attended or unattended). This was seen on three separate Xenial clouds. Both Mitaka and Ocata. The package upgrade today was to pacemaker 1.1.14-2ubuntu1.2. It appears that pacemaker.prerm stops the service using "invoke-rc.d pacemaker stop" and then the pacemaker.postinst attempts to start the service, but silently fails due to policy denial. It appears the policy check fails because /etc/rcX.d/S*pacemaker does not exist because /etc/init.d/pacemaker has no Default-Start or Default-Stop entries in the LSB init headers. (or rather, they are blank.) I have not checked whether this affects trusty environments. I'd suggest on systems that use systemd, the pacemaker.postinst script should check if the service is enabled and start it with systemctl commands rather than using the cross-platform compatible invoke-rc.d wrappers. Or upstream pacemaker should get default start/stop entries. Our default runlevel on cloud init built images appears to be 5 (graphical), so at least 5 should be present in /etc/init.d/pacemaker LSB init headers under Default-Start:.
2017-10-25 10:51:42 Stevie Beth Mhaol bug added subscriber Stephen Shirley
2017-10-25 11:18:46 Launchpad Janitor pacemaker (Ubuntu Xenial): status Triaged Fix Released
2017-10-25 11:18:52 Andy Whitcroft removed subscriber Ubuntu Stable Release Updates Team
2017-10-25 12:38:21 Ubuntu Foundations Team Bug Bot tags canonical-bootstack canonical-is cpe-onsite pacemaker sts canonical-bootstack canonical-is cpe-onsite pacemaker patch sts
2017-10-25 13:11:08 Ryan Beisner tags canonical-bootstack canonical-is cpe-onsite pacemaker patch sts canonical-bootstack canonical-is cpe-onsite pacemaker patch sts uosci
2017-10-25 13:24:39 Stevie Beth Mhaol removed subscriber Stephen Shirley
2017-10-25 15:49:07 Launchpad Janitor init-system-helpers (Ubuntu): status New Confirmed
2017-10-25 15:49:07 Launchpad Janitor init-system-helpers (Ubuntu Xenial): status New Confirmed
2017-10-25 15:49:07 Launchpad Janitor init-system-helpers (Ubuntu Zesty): status New Confirmed
2017-10-25 15:49:07 Launchpad Janitor init-system-helpers (Ubuntu Artful): status New Confirmed
2017-10-26 21:43:08 Dean Henrichsmeyer bug added subscriber Canonical Field High
2017-10-27 07:30:26 Christian Ehrhardt  bug added subscriber ChristianEhrhardt
2017-11-28 18:09:45 David Britton removed subscriber Canonical Field High
2017-11-28 18:10:32 David Britton bug task deleted init-system-helpers (Ubuntu Bionic)
2017-11-28 18:10:38 David Britton bug task deleted init-system-helpers (Ubuntu Artful)
2017-11-28 18:10:44 David Britton bug task deleted init-system-helpers (Ubuntu Zesty)
2017-11-28 18:10:50 David Britton bug task deleted init-system-helpers (Ubuntu Xenial)
2017-11-28 18:11:04 David Britton init-system-helpers (Ubuntu): status Confirmed Opinion
2017-11-29 01:26:52 Dean Henrichsmeyer bug added subscriber Canonical Field High