Nish Aravamudan <nish.aravamu...@canonical.com> writes: >> Nishanth Aravamudan <nish.aravamu...@canonical.com> writes: >> >>> Now, neither of these actually fix the existing packages >>> unfortunately, which will stop pacemaker on the upgrade to a fixed >>> package and thus stop pacemaker. I have no idea if there actually is >>> any way to fix this for existing packages, since the 'old' prerm >>> will be invoked by dpkg on the upgrade path. > > in theory if a fix lands, its the last time this happens
I have to make a correction here. The problem is not that Pacemaker is stopped when Corosync is upgraded, but that Pacemaker is not started after the Corosync upgrade is complete. So the old prerm stopping Corosync is not a problem: the new postinst will *restart* Corosync (even though it's stopped already), and the restart operation does start Pacemaker again. A simple start operation does not, but a restart does. I haven't decided yet whether this is a systemd bug, a quirk or a feature. -- Regards, Feri
