Bug#887563: corosync prerm will stop pacemaker and not start it again

Nish Aravamudan writes: >> Nishanth Aravamudan 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

Bug#887563: corosync prerm will stop pacemaker and not start it again

Nish Aravamudan writes: > I spent some time reading the manpage myself and this is how I > interpret the relevant section(s): > > Requires= >Configures requirement dependencies on other units. If this unit >gets activated, the units

Bug#887563: corosync prerm will stop pacemaker and not start it again

Hi Ferenc! On Fri, Apr 20, 2018 at 7:59 AM, Ferenc Wágner wrote: > Control: fixed -1 2.4.4-1 > > Nishanth Aravamudan writes: > >> I believe this is because the prerm of corosync.service [...] >> unconditionally stops corosync for all Debian and

Bug#887563: corosync prerm will stop pacemaker and not start it again

Control: fixed -1 2.4.4-1 Nishanth Aravamudan writes: > I believe this is because the prerm of corosync.service [...] > unconditionally stops corosync for all Debian and Ubuntu releases > (as the init script is installed even if unused by systemd). When > corosync

Bug#887563: corosync prerm will stop pacemaker and not start it again

Control: found 887563 2.4.2-3 Control: severity 887563 important This just bit me on a Stretch cluster when upgrading corosync from 2.4.2-3 to 2.4.2-3+deb9u1. Marking as such. Please apply the suggested fixes as soon as possible. Anders

Bug#887563: corosync prerm will stop pacemaker and not start it again

Source: corosync Severity: normal Dear Maintainer, We have a report in Ubuntu, https://bugs.launchpad.net/charm-hacluster/+bug/1740892, which I believe is reproducible in Debian Sid as well. In particular, I set up a Sid LXD: # apt install corosync pacemaker ... # systemctl status corosync