7.213. rgmanager

Bug Fixes

BZ#825375

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#831658

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#833347

Previously, the cpglockd init script was not included in the chkconfig configuration file. This updated adds cpglockd in this file.

BZ#853251

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#861157

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#879031

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.