8.163. pacemaker

Bug Fixes

BZ#1036631

Previously, co-location constraints for cloned groups were not fully respected. As a consequence, members of cloned groups were not correctly stopped along with dependencies. Now, members of cloned groups are stopped whenever dependencies are also stopped.

BZ#1037423

Prior to this update, no information concerning the status of healthy members of a cloned resource group were displayed to the user. A new option has been added to allow the status of cloned groups to be shown in the output of the "pcs status --full" command.

BZ#1046131

Previously, Pacemaker did not correctly cancel the recurring monitor operation of LSB scripts it managed. Consequently, monitor operations failed after resources successfully stopped. This bug has been fixed, and recurring monitor operations are now correctly cancelled before the LSB resource is stopped.

BZ#1069279

Under some conditions, the default stop or start ordering of resources enabled violation of co-location constraints. As a consequence, resources could be temporarily active on the same node despite a colocation constraint that instructed them otherwise. With this update, ordering of resources respects configured colocation constraints, and resources are never on the same node if configured not to be.

BZ#1078954

Previously, Pacemaker could not start more than 10 instances of a cloned resource. As a consequence, clusters containing more than 10 nodes did not function correctly. This update fixes this bug, and Pacemaker can now properly start an unlimited number of instances of a cloned resource.

BZ#1086885

Due to a timing issue, nodes that rebooted too fast became stuck in the pending state and did not rejoin the cluster. With this update, the timing issue has been resolved, nodes now join the cluster, and are reported as online.