Issued:
2013-01-07
Updated:
2013-01-07

RHBA-2013:0026 - rgmanager bug fix update

Synopsis

rgmanager bug fix update

Type/Severity

Bug Fix Advisory

Topic

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

Description

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:

  • A mirror device failure during the relocation of the High Availability LVM service (HA-LVM) could cause, under certain circumstances, the service to fail. This bug has been fixed and now the mirror device failure no longer affects the HA-LVM service in such a case. (BZ#693855)

  • The orainstance.sh resource agent did not detect all startup failures properly. The underlying source code has been modified and all failures are now detected correctly. (BZ#723819)

  • LVM resource agent could not update logical volume tags if there were missing physical volumes. This bug has been fixed and the logical volume tags are forcibly removed if the physical volumes are missing. (BZ#756180)

  • If the cman service was stopped while the rgmanager service was running, rgmanager sometimes exited uncleanly without releasing its Distributed Lock Manager (DLM) lock space. Consequently, it was impossible to shut down rgmanager and cman. Now if the user mistakenly attempts to stop cman service while rgmanager is still running, rgmanager no longer stops in this situation. (BZ#769730)

  • If the /etc/lvm/lvm.conf file was changed after the last initrd (initial ramdisk) rebuild, the LVM resource agent failed. This agent has been modified to generate a warning message and no longer fails in such a case. (BZ#773372)

  • If a service with a relocate failover policy failed and the relocation operation failed as well, the service could be restarted locally. Due to an error in the source code, the service afterwards stopped, even if the local restart succeeded. This error has been fixed, and these services no longer stop after a successful local restart. (BZ#789366)

  • When the root file system was full, rgmanager randomly killed applications when trying to force-unmount. The underlying source code has been modified and applications are stopped instead of killed in this case. (BZ#819595)

  • Under rare conditions, rgmanager attempted to free memory that had been previously freed. As a consequence, rgmanager terminated unexpectedly with a segmentation fault. This bug has been fixed and rgmanager no longer attempts to free previously-freed memory. (BZ#820632)

  • 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 recovery of a service that had failed its start operation. This bug has been fixed and rgmanager works as expected. (BZ#834459)

  • If the contents of the /proc/mounts file changed during a status check operation of the file system resource agent, the status check could incorrectly detect that a mount was missing and mark a service as failed. This bug has been fixed and rgmanager's file system resource agent no longer reports false failures in the described scenario. (BZ#847125)

This update also adds the following enhancements:

  • A new "prefer_interface" parameter has been added to the rgmanager ip.sh resource agent. This parameter is used for adding an IP address to a particular network interface if a cluster node has multiple active interfaces that have IP addresses on the same subnetwork. (BZ#819494)

  • In some cases, "fs unmount" command and clustersfs resource agents were unable to unmount the file systems which were exported by the nfsd utility. The new nfsrestart option to enable a last resort workaround prior to failing to unmount the file system has been added. The new option requires force_unmount="" to be enabled and it is not compatible with nfsserver resource agent. (BZ#822066)

All users of rgmanager should upgrade to these updated packages, which fix these bugs and add these enhancements.

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

ProductVersionArch
Red Hat Enterprise Linux High Availability for x86_645x86_64
Red Hat Enterprise Linux High Availability for x86_645ppc
Red Hat Enterprise Linux High Availability for x86_645ia64
Red Hat Enterprise Linux High Availability for x86_645i386
Red Hat Enterprise Linux High Availability (for RHEL Server) from RHUI5x86_64
Red Hat Enterprise Linux High Availability (for RHEL Server) from RHUI5i386

Updated Packages

  • rgmanager-debuginfo-2.0.52-37.el5.ppc.rpm
  • rgmanager-2.0.52-37.el5.i386.rpm
  • rgmanager-2.0.52-37.el5.x86_64.rpm
  • rgmanager-2.0.52-37.el5.ia64.rpm
  • rgmanager-2.0.52-37.el5.ppc.rpm
  • rgmanager-2.0.52-37.el5.src.rpm
  • rgmanager-debuginfo-2.0.52-37.el5.i386.rpm
  • rgmanager-debuginfo-2.0.52-37.el5.ia64.rpm
  • rgmanager-debuginfo-2.0.52-37.el5.x86_64.rpm

Fixes

CVEs

(none)

References

(none)

Additional information