RHBA-2014:1544 - Bug Fix Advisory

Topic

Updated pacemaker packages that fix several bugs are now available for Red Hat
Enterprise Linux 6.

Description

The Pacemaker 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, 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#1036631)

• 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#1037423)

• 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#1046131)

• 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#1069279)

• 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#1078954)

• 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.
(BZ#1086885)

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

Solution

Before applying this update, make sure all previously released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/articles/11258

Affected Products

• Red Hat Enterprise Linux High Availability for x86_64 6 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 6 i386
• Red Hat Enterprise Linux Resilient Storage for x86_64 6 x86_64
• Red Hat Enterprise Linux Resilient Storage for x86_64 6 i386
• Red Hat Enterprise Linux High Availability (for RHEL Server) from RHUI 6 x86_64
• Red Hat Enterprise Linux High Availability (for RHEL Server) from RHUI 6 i386
• Red Hat Enterprise Linux Resilient Storage (for RHEL Server) from RHUI 6 x86_64
• Red Hat Enterprise Linux Resilient Storage (for RHEL Server) from RHUI 6 i386

Fixes

• BZ - 1020210 - crm_master ignores option to specify nodename
• BZ - 1036631 - cloned group constraints are not respected on disable
• BZ - 1037423 - pcs does not correctly display status for cloned resource groups
• BZ - 1046131 - pacemaker LSB agent resources do not have recurring monitor operations canceled correctly.
• BZ - 1069279 - Prevent resources in an anti-colocation from even temporarily running on a same node
• BZ - 1069795 - Under certain circumstances pacemaker can create node entries for unknown nodes
• BZ - 1071995 - pacemaker rebase
• BZ - 1071996 - pacemaker_remote support
• BZ - 1078954 - clone resources do not start on all nodes in 16-node cluster
• BZ - 1106841 - Missing dependency on shadow-utils (and possibly more)
• BZ - 1113189 - pacemaker should list glib2-2.28 as a dependency

CVEs

(none)

References

(none)