[ClusterLabs] corosync.service (and sbd.service) are not stopper on pacemaker shutdown when corosync-qdevice is used

[Andrei Borzenkov]

On Mon, Jul 29, 2019 at 9:52 AM Jan Friesse <jfriesse at redhat.com> wrote:
>
> Andrei
>
> Andrei Borzenkov napsal(a):
> > corosync.service sets StopWhenUnneded=yes which normally stops it when
>
> This was the case only for very limited time (v 3.0.1) and it's removed
> now (v 3.0.2) because it was causing more troubles than it was worth.
>

So I was unlucky to catch this specific version :)

Thanks for explanation.

> Regards,
>    Honza
>
> > pacemaker is shut down. Unfortunately, corosync-qdevice.service declares
> > Requires=corosync.service and corosync-qdevice.service itself is *not*
> > stopped when pacemaker.service is stopped. Which means corosync.service
> > remains "needed" and is never stopped.
> >
> > Also sbd.service (which is PartOf=corosync.service) remains running as well.
> >
> > The latter is really bad, as it means sbd watchdog can kick in at any
> > time when user believes cluster stack is safely stopped. In particular
> > if qnetd is not accessible (think network reconfiguration).
> > _______________________________________________
> > Manage your subscription:
> > https://lists.clusterlabs.org/mailman/listinfo/users
> >
> > ClusterLabs home: https://www.clusterlabs.org/
> >
>