3.76. rgmanager

Bug Fixes

BZ#853083

When a cluster configuration file was invalid, an attempt to run the "clustat" command failed with a segmentation fault. This bug has been fixed with this update and "clustat" no longer crashes in the described scenario.

BZ#997546

Previously, the cluster services file system failed over from one node to another if the /tmp/ directory filled up. A patch has been provided to fix this bug and cluster services no longer fail over.

BZ#1016784

Recent changes in the lvm_by_lv script introduced a bug that caused all Logical Volume Management (LVM) status checks to fail. Consequently, when using high availability LVM (HA-LVM) with tagging made by LV, multiple warning and error messages were emitted while attempting to start a configured LVM resource. The LVM resource subsequently failed to start with a "vg/lv should not be active" error message. With this update, lvm_by_lv has been modified to remove white spaces from lvm commands that determine the resource owner. LVM status checks now succeed as expected and LVM resources are started properly.

BZ#1020279

Due to a syntax error in the underlying source code, the "find" command failed to find files whose names ended with the ".img" suffix. This update applies a patch to fix this bug and the command now works as expected.

BZ#1022723

If the "listener_name" attribute was omitted for the oracledb.sh resource agent script, the oracledb resources failed to start. With this update, oracledb.sh has been modified to operate correctly when no "listener_name" is given, and thus now starts as expected.

BZ#1035023

In certain environments, the hard-coded sleep time used in the agent process before trying to connect to the postmaster process was not long enough. As a consequence, the postgres-8 service terminated unexpectedly. With this update, the postgres-8.sh script has been modified to allow users to configure the sleep time according to their needs.

BZ#1035034

Under certain conditions, the postgres-8 service did not shut down gracefully and left the PID file populated. Consequently, the service failed to start after the reboot. The underlying source code has been modified and postgres-8 now works as expected.

BZ#1047989

Previously, the oralistener resource agent failed to stop when the listener process was no longer running. This update provides a patch to fix this bug and oralistener works correctly in the described scenario.

Enhancement

BZ#924694

This update adds the possibility to specify the "timeout" parameter for the Xen virtual machines when using the "xm" command.