pacemaker-1.1.16-12.el7.4

The Pacemaker cluster resource manager is a collection of technologies working
together to provide data integrity and the ability to maintain application
availability in the event of a failure.

This update fixes the following bugs:

* Previously, Pacemaker did not implement unfencing for Pacemaker remote nodes. As a consequence, Pacemaker remote nodes remained fenced even if a fence device required unfencing. With this update, Pacemaker correctly implements both fencing and unfencing for Pacemaker remote nodes, and the described problem no longer occurs. (BZ#1491544)

* Previously, Pacemaker's bundle implementation was not applied correctly. As a consequence, multiple errors occurred. When using bundles, a bundle was not running on a Pacemaker remote node. Resource agents that required clone notifications were not running properly inside a bundle. When running inside a bundle, resource agents were not able to know whether node attributes could be set on the bundle node or on their underlying host. Also, colocation constraints involving bundles did not work properly. This bug has been fixed, and the mentioned capabilities now work as expected. (BZ#1497602)

Users of pacemaker are advised to upgrade to these updated packages, which fix
these bugs.