RHBA-2013:0409 - Bug Fix Advisory

Topic

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

Description

The rgmanager packages contain the Red Hat Resource Group Manager, which allows
to create and manage high-availability server applications in the event of
system downtime.

This update fixes the following bugs:

• Due to an unlocked access to internal DBus data structures from different

rgmanager threads, rgmanager could terminate unexpectedly inside dbus library
functions when running rgmanager without the "-q" flag (set as default). The
underlying source code has been modified and rgmanager no longer fails in this
situation. (BZ#825375)

• Previously, rgmanager preferred two nodes in a three-nodes cluster, which

caused the third node being unused. The configuration has been changed and
rgmanager now uses all nodes in the cluster as expected. (BZ#831658)

• Previously, the cpglockd init script was not included in the chkconfig

configuration file. This updated adds cpglockd in this file. (BZ#833347)

• Resource Group Manager fails to stop a resource if it is located on an

unmounted file system. As a result of this failure, rgmanager treated the
resource as missing and marked the appropriate service as failed, which
prevented the cluster from recovering the service. This update allows rgmanager
to ignore this error if a resource has not been previously started with a
service. The service can now be properly started on a different host.
(BZ#853251)

• When rgmanager received a remote start message for a particular service while

already in the process of starting that service locally, a deadlock could occur.
This sometimes happened during the recovery of a service that had failed its
start operation. This bug has been fixed and rgmanager works as expected.
(BZ#861157)

• When a service is configured with a recoverable resource, such as nfsclient, a

failure of that client correctly triggers the recovery function. However, even
if recovery operation was successful, rgmanager still stopped and recovered the
service. The underlying source code has been modified and rgmanager no longer
stops successfully recovered clients. (BZ#879031)

All users of rgmanager 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/knowledge/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 - 825375 - dbus-related crash in rgmanager
• BZ - 831648 - rgmanager prefers 2 nodes in 3 nodes cluster
• BZ - 833347 - cpglockd init script is not added to chkconfig db

CVEs

(none)

References

(none)