rgmanager bug fix and enhancement update

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

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

This update fixes the following bugs:

* Previously, rgmanager incorrectly called the rg_wait_threads() function during
cluster reconfiguration. This could lead to an internal deadlock in rgmanager
which caused the cluster services to become unresponsive. This irrelevant call
has been removed from the code and deadlocks now no longer occur during cluster
reconfiguration. (BZ#635152)

* When enabling a service using the clusvcadm command with the "-F" option,
rgmanager did not update the service owner information before responding to
clusvcadmn. Consequently, clusvcadm could print incorrect information about
which cluster node the service was running on. This update modifies rgmanager to
update the owner information prior to responding to clusvcadm, and the command
now provides the correct information. (BZ#727326)

* Under certain circumstances, a "stopped" event could be processed after a
service and its dependent services had already been restarted. This forced the
dependent services to restart erroneously. This update allows rgmanager to
ignore the "stopped" events if dependent services have already been started, and
the services are no longer restarted unnecessarily. (BZ#743218)

* Resource Group Manager did not handle certain inter-service dependencies
correctly. Therefore, if a service was dependent on another service that was
running on the same cluster node, the dependent service became unresponsive
during the service failover and remained in the recovering state. With this
update, rgmanager has been modified to check a service state during failover and
stop the service if it is dependent on the service that is failing over.
Resource Group Manager then tries to start this dependent service on other nodes
as expected. (BZ#744824)

* The "-F" option of the clusvcadm command allows rgmanager to start a service
according to failover domain rules. This option was not previously described in
the command's manual pages. With this update, the "-F" option has been properly
documented in the clusvcadm(8) manual page. (BZ#745226)

* Previously, if a newly added service failed to start on the first cluster
node, rgmanager could try to relocate the service to another cluster node before
the cluster configuration was updated on that node. Consequently, the service
was set to the "recovering" state and had to be manually re-enabled in order to
start. This update modifies rgmanager to retry the relocation process until
after the cluster configuration has been updated on the node. The service can
now be relocated as expected. (BZ#796272)

* Due to an invalid pointer dereference, rgmanager could terminate unexpectedly
with a segmentation fault when central processing mode was enabled on a cluster
node. With this update, the pointer dereference has been corrected, and
rgmanager no longer crashes when central processing mode is enabled. (BZ#803474)

* Previously, in central processing mode, rgmanager failed to restart services
that depended on a service that failed and was recovered. With this update,
during the recovery of a failed service, any services that depend on it are
restarted. (BZ#807165)

In addition, these updated rgmanager packages provide the following enhancement:

* This update introduces a feature which enables rgmanager to utilize Corosync's
Closed Process Group (CPG) API for inter-node locking. This feature is
automatically enabled when Corosync's Redundant Ring Protocol (RRP) feature is
enabled. Corosync's RRP feature is considered fully supported. However, when
used with the rest of the High-Availability Add-Ons, it is considered a
Technology Preview. (BZ#799505)

Users are advised to upgrade to these updated rgmanager packages, which fix
these bugs and add this enhancement.

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

635152 - rgmanager[4188]: #37: Error receiving header from 1 sz=0 CTX 0x240a130
743218 - Cluster problem: "hard" service dependencies
745226 - clusvcadm does not have the -F option documented in man page
796272 - service configuration update occurred out of sync