Tell the cluster to stop managing services. This is required to allow the services to remain active after the cluster shuts down.
# crm_attribute -t crm_config -n is-managed-default -v false
For any resource that has a value for is-managed, make sure it is set to false so that the cluster will not stop it (replacing $rsc_id appropriately):
# crm_resource -t primitive -r $rsc_id -p is-managed -v false
On each node:
Shutdown the cluster software (pacemaker and the messaging layer).
Upgrade the Pacemaker software. This may also include upgrading the messaging layer and/or the underlying operating system.
Check the configuration manually or with the crm_verify tool if available.
On each node:
Start the cluster software. The messaging layer can be either Corosync or Heartbeat and does not need to be the same one as before the upgrade.
Verify that the cluster re-detected all resources correctly.
Allow the cluster to resume managing resources again:
# crm_attribute -t crm_config -n is-managed-default -v true
For any resource that has a value for is-managed, reset it to true (so the cluster can recover the service if it fails) if desired:
# crm_resource -t primitive -r $rsc_id -p is-managed -v true
