Comment 9 for bug 1903745

Big problem with corosync and pacemaker packages is that they don't put resources into unmanaged state before upgrade. Hitting an issue like this is also tightly related to configuration of the pacemaker/corosync. Upgrading corosync, without stopping pacemaker (and therefore lrmd) has high probability to result with this behaviour. In the end, corosync is only a messaging bus.

So the upgrade procedure should really be:
1) put pacemaker's resource into unmanaged mode
2) stop pacemaker
3) upgrade corosync
4) restart corosync
5) start pacemaker
6) put resources into managed mode

Steps 3 & 4 are automatically done by corosync upgrade package, but all other steps are left to the operator. If upgrade is done by unattended upgrades, this will quite likely happen again.