Bug 2189301

.Rebase Pacemaker packages to version: 2.1.6 The Pacemaker packages have been upgraded to upstream version 2.1.6, which provides a number of enhancements and bug fixes over the previous version. The following features have been added: * Previously, when a Pacemaker Remote connection was lost, Pacemaker would always purge its transient node attributes. This was unnecessary if the connection was quickly recoverable and the remote daemon had not restarted in the meantime. Pacemaker Remote nodes now preserve transient node attributes after a brief, recoverable connection outage. * The `alert_snmp.sh.sample` alert agent, which is the sample alert agent provided with Pacemaker, now supports the SNMPv3 protocol as well as SNMPv2. With this update, You can copy the `alert_snmp.sh.sample` agent without modification to use SNMPv3 with Pacemaker alerts. * Pacemaker alerts and alert recipients now support an `enabled` meta option. Setting this option to `false` for an alert disables the alert. Setting this option to `true` for an alert and `false` for a particular recipient disables the alert for that recipient. The default value for this option is `true`. You can use this option to temporarily disable an alert for any reason, such as planned maintenance. The following bugs have been fixed: * Pacemaker Designated Controller elections no longer finalized until all pending actions are complete and no action results are lost. * The `fence_scsi` agent is now able to auto-detect shared `lvmlockd` devices when the 'devices' attribute is not set. * Resource stickiness now properly compares against colocation scores. * The `crm_resource` command now allows banning or moving a bundle with only a single active replica. * Previously, promotable clone instances were assigned in numerical order, with promoted instances first. As a result, if a promoted clone instance needed to start, an unpromoted instance in some cases restarted unexpectedly, because the instance numbers changed. With this fix, roles are considered when assigning instance numbers to nodes and as a result no unnecessary restarts occur.