RHBA-2004:122 - Bug Fix Advisory
Updated clumanager and redhat-config-cluster packages fix various bugs
Bug Fix Advisory
Updated Red Hat Cluster Manager (clumanager, redhat-config-cluster)
packages that fix various bugs are now available for Red Hat Enterprise
Red Hat Cluster Manager provides high availability of critical server
applications in the event of planned or unplanned system downtime.
Various bugs in Red Hat Cluster Manager have been discovered and addressed
since the release of Red Hat Enterprise Linux 3, including:
- Add PyXML to the RPM spec file 'Requires:' line.
- Fix to allow changing daemon properties in clusters where the member
count is not 2 or 4.
- Add status window to redhat-config-cluster during service migration.
- Fix for service outage on disconnect of fibre channel cable.
- Fix typos and logic errors in svclib_filesystem which could cause ill
behavior in error conditions.
- Fix force unmount support when used with lsof.
- Don't reboot if joining the multicast group fails.
- Don't allow formation of new quorum in IP-tiebreaker clusters without a
strict majority of real members.
- Add 'cluforce(8)' command to allow administrator override in even-split case.
- Fix for clusters using two RPS-10s.
Users of Red Hat Cluster Manager are advised to upgrade to these updated
packages, which resolve these issues.
Performing a Cluster Upgrade
This erratum can be upgraded in a "rolling" fashion. That is, it is
possible to upgrade the cluster software without taking the entire cluster
offline at once. Due to a bugfix between 1.2.3 and 1.2.9, however, it is
necessary to upgrade the lowest-ordered member last. (If you are upgrading
from 1.2.9, you may upgrade the members in any order; the instructions
below assume you are running clumanager version 1.2.3.)
Notes (Before you begin):
- All cluster members must be running and participating in the cluster
quorum, or no members should be running at all.
- Is a good idea to perform this upgrade during scheduled maintenance
and/or when it will impact the fewest number of users.
Steps (with all cluster members running):
(1) Run the following:
# cludb -g members%member0%name
The host displayed is the lowest-ordered cluster member. This member must
be upgraded *last*.
If this member is "not found", look at /etc/cluster.xml. Look for the
"member" tag with the lowest "id" property; this is the lowest-ordered member.
Make a note of this member; this member must be upgraded last.
(2) Run 'rpm -Fvh [filenames]' (as noted above) on all cluster members
except the member noted in step (1), one at a time. Do not execute this
command on multiple members simultaneously, as the upgrade process disables
a member temporarily (removing it from the cluster quorum). If too many
members are disabled simultaneously, the cluster quorum will no longer
exist, forcing services managed by the cluster software to become
Services located on a member that is being upgraded will migrate to other
cluster members whenever possible.
(3) Run 'rpm -Uvh [filenames]' on the member noted in step (1).
(4) If desired, balance cluster services across available members using
redhat-config-cluster or clusvcadm.
(5) Run 'chkconfig --add clumanager' on all members.
Steps (No cluster members running the cluster software):
(1) Run 'service clumanager stop' on all members.
(2) Run 'rpm -Uvh [filenames]' on all members.
(3) Run 'chkconfig --add clumanager' on all members.
(4) Restart the cluster software on all members if desired.
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you
can also use wildcards (*.rpm) if your current directory *only* contains
the desired RPMs.
Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
If up2date fails to connect to Red Hat Network due to SSL
Certificate Errors, you need to install a version of the
up2date client with an updated certificate. The latest version of
up2date is available from the Red Hat FTP site and may also be
downloaded directly from the RHN website:
- Red Hat Enterprise Linux High Availability for x86_64 3 i386
- BZ - 112933 - redhat-config-cluster should depend on PyXML
- BZ - 113226 - Service outage on disconnect of fibre channel cable
- BZ - 113503 - [PATCH] Daemon properties won't allow changes in 3-member clusters
- BZ - 114435 - svclib_filesystem shell-script include file - problems with
- BZ - 114653 - clumanager should not run if joining the multicast group fails
- BZ - 114920 - Taroon Clustering: Redhat-config-cluster does not work as it should
- BZ - 115013 - PATCH: typo prevents use of lsof in forced umount support
- BZ - 116012 - Taroon Clustering: After a node reboots and re-joins a cluster it grabs the services from the other node
- BZ - 116380 - Two serial powercontrollers on the same port on two different nodes are not accepted
Red Hat Enterprise Linux High Availability for x86_64 3