8.177. resource-agents
Updated resource-agents packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The resource-agents packages contain a set of scripts to interface with several services to operate in a High Availability environment for both Pacemaker and rgmanager service managers.
Bug Fixes
- BZ#784933
- Previously, when the
exportfs
utility was used to relocate an exported share, the size of the/var/llib/nfs/rmtab
file was doubled. This bug has been fixed and the/var/lib/nfs/rmtab
file size is no longer doubled in the aforementioned scenario. - BZ#851188
- Prior to this update, the
fs-lib.sh
agent did not recognize the trailing slash ("/") character when searching for devices in the/proc/mounts
file. Consequently, NFSv4 mounts were not monitored. With this update,fs-lib.sh
has been modified to track the slash characters. As a result, NFSv4 mounts are managed and monitored as expected. - BZ#853220
- Due to a bug in the
oracledb.sh
script, when there were multiple ORACLE instances running in the same home directory, the script produced unnecessary delays. The bug has been fixed, andoracledb.sh
now works without delays when multiple ORACLE instances are present in the home directory. - BZ#871659
- To shutdown cleanly, the
postgres
agent needs to receive the SIGINT signal. Previously, this signal was not sent andpostgres
performed a hard shutdown instead of a graceful exit. This behavior has been modified, and SIGINT is now sent topostgres
on shutdown to attempt a graceful exit, and after a period of time, the SIGQUIT signal is sent if the agent is still active. As a result,postgres
performs graceful shutdown during the stop action. - BZ#884326
- Previously, if a device failed in a non-reduntant (that is not mirror or RAID) logical volume (LV) that was controlled by the HA-LVM utility, the entire LV could be automatically deleted from the volume group. This bug has been fixes and now, if a non-redundant logical volume suffers a device failure, HA-LVM fails to start the service rather than forcing the removal of failed LVs from the volume group.
- BZ#895075
- Prior to this update, the
ip.sh
agent did not configure IPv6 addresses that contained upper-case letters. Consequently, a resource with such an address failed. With this update,ip.sh
has been modified to be case insensitive for IPv6 addresses. As a result, IPv6 addresses with upper case letters are now configured properly byip.sh
. - BZ#908457
- Previously, agents based on the
fs-lib.sh
script, such asip.sh
, ignored theself_fence
option when theforce_unmount
option was enabled. Consequently, the configuredself_fence
option was not enabled. This bug has been fixed andself_fence
is accepted regardless offorce_unmount
. - BZ#948730
- With this update, the priority level of log messages produced by the
mount
utility has been changed from previouserror
to more appropriatedebug
level. - BZ#959520
- Due to an incorrect SELinux context of the
/var/lib/nfs/statd/sm/
directory, therpc.statd
daemon was unable to start. This problem only appeared if the cluster included NFS mounts. This update modifies how files are copied to the/var/lib/nfs/statd/sm/
directory, so that the SELinux context is inherited from the target directory. As a result,rpc.statd
can now be started without complications. - BZ#974941
- When
autofs
maps are used for network storage, agents for cluster file systems ("fs") such as netfs.sh, fs.sh, or clusterfs.sh require theuse_findmnt
option set to'false'
. Previously, whenuse_findmnt
was set incorrectly, andautofs
maps became unavailable, the rgmanager services with "fs" resources consequently became unresponsive until the network was restored. The underlying source code has been modified and rgmanager services no longer hang in the aforementioned scenario. - BZ#976443
- Prior to this update, the
lvm.sh
agent was unable to accurately detect a tag represented by a cluster node. Consequently, the active logical volume on a cluster node failed when another node rejoined the cluster. With this update,lvm.sh
properly detects whether tags represent a cluster node. As a result, when nodes rejoin the cluster, the volume group no longer fails on other nodes. - BZ#981717
- When multiple instances of the
tomcat-6
service were used as cluster resources, theTOMCAT_USER
setting in custom/conf/tomcat6.conf
configuration files was ignored. Consequently, each instance always started withTOMCAT_USER
set toroot
. This bug has been fixed, andTOMCAT_USER
is now applied properly in the described case. - BZ#983273
- Under certain circumstances, when the
tomcat.conf
configuration file for atomcat-6
resource was stored on a shared storage resource that became unavailable, the subsequent stop operation ontomcat-6
failed. This bug has been fixed, andtomcat-6
can now be successfully stopped whentomcat.conf
is not readable. - BZ#998012
- File system based resources, such as
fs.sh
orclusterfs.sh
, required usage of the/tmp
directory during status monitoring. If this directory became full after mounting the file system, the monitor action failed even though the file system was correctly mounted. The/tmp
directory is no longer used during file system monitors, thus fixing this bug. - BZ#1009772
- If rgmanager was started simultaneously on two nodes, these nodes could both execute the
lvchange --deltag
command at the same time and corrupt the LVM headers. With this update, LVM headers do not become corrupt even when rgmanager stars on two nodes at the same time. - BZ#1014298
- Previously, when the NFS server was unresponsive, the fuser utility could block the unmounting of an NFS file system. With this update, fuser has been replaced with custom logic that searches for processes with open file descriptors to an NFS mount, thus fixing this bug.
Enhancements
- BZ#670022
- With this update, support for Oracle Database 11g has been added to the
oracledb
,orainstance
, andoralistener
resource agents. - BZ#711586
- This update adds the new
update-source
option to thenamed.sa
agent. With this option enabled, it is possible to set thenotify-source
,transfer-source
, andquery-source
to the service cluster IP. - BZ#909954
- With this update, the lock file for the
/usr/share/cluster/orainstance.sh
script has been moved from the/tmp/
directory to/var/tmp/
. - BZ#917807
- With this update, the
TNS_ADMIN
variable has been added to theoracledb.sh
cluster script. This variable is a standard Oracle feature to set a specific path to the listener configuration file. - BZ#919231
- This update improves performance of start, stop, and monitor actions for file system resources. The file system resources use of the findmnt utility to speed up migrations on clusters with a large amount of file system resources.
- BZ#989284
- This update adds official support for the ocf heartbeat resource agents required for use with the Pacemaker cluster manager. Only officially supported agents are present for this initial release. This means heartbeat agents lacking official support are not shipped in this update.
Users of resource-agents are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.
Updated resource-agents packages that fix two bugs are now available for Red Hat Enterprise Linux 6.
The resource-agents packages contain a set of scripts to interface with several services to operate in a High Availability environment for both Pacemaker and rgmanager service managers.
Bug Fixes
- BZ#1027410
- Prior to this update, the netfs agent could hang during a stop operation, even with the self_fence option enabled. With this update, self fence operation is executed sooner in the process, which ensures that NFS client detects server leaving if umount can not succeed, and self fencing occurs.
- BZ#1027412
- Previously, the IPaddr2 agent did not send out unsolicited neighbor advertisements to announce a link-layer address change. Consequently, floating IPv6 addresses, which require this functionality, could not work correctly. To fix this bug, the send_ua internal binary required for IPaddr2 agent to drive IPv6 addresses has been added. As a result, the floating IPv6 addresses now work correctly, and IPv4 addresses are left unaffected by this change.
Users of resource-agents are advised to upgrade to these updated packages, which fix these bugs.