Comment 11 for bug 1740892

Based on #10 and some testing I did early today, it really feels like this might be a bug in pacemaker when re-connecting to corosync after a restart; I think there are two ways forward on this:

a) corosync package updates should always restart pacemaker
b) we should look for a fix in pacemaker to make it more resilient to corosync restarts

either would have prevented this issue from occurring in the first place.