- Issued:
- 2004-01-26
- Updated:
- 2004-01-26
RHBA-2003:331 - Bug Fix Advisory
Synopsis
Updated clumanager packages fix various bugs
Type/Severity
Bug Fix Advisory
Topic
Updated Red Hat Cluster Manager (clumanager) packages that fix various bugs
are now available for Red Hat Enterprise Linux 3.
Description
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:
- Internationalization fixes for redhat-config-cluster
- Inclusion of man pages for previously undocumented commands
- Handles "ifdown [cluster interface]" properly.
- Handles loss of IP tie-breaker for 2 and 4 member clusters.
- Does not start disk tie-breaker thread when IP tie-breaker is in use
(wastes resources).
- Monitors cluster-managed IP addresses and file systems when service
monitoring is in use.
- Fixes split-brain behavior which occurred when disk-based tie-breaker was
used and both members are started while no intracluster network
communication is available.
- Fixes services not failing over when lock master (lowest-ordered member)
reboots in the middle of a lock write (for instance, when it loses access
to shared storage during a write request).
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, however, it is necessary to upgrade the
lowest-ordered member last.
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 people.
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
unavailable.
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.
Solution
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:
up2date
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:
Affected Products
- Red Hat Enterprise Linux Server 3 x86_64
- Red Hat Enterprise Linux Server 3 ia64
- Red Hat Enterprise Linux Server 3 i386
- Red Hat Enterprise Linux for IBM z Systems 3 s390x
- Red Hat Enterprise Linux for IBM z Systems 3 s390
- Red Hat Enterprise Linux for Power, big endian 3 ppc
Fixes
- BZ - 106465 - Clustering -- Missing man pages
- BZ - 106498 - ifdown [primary_interface] is not detected by cluster software
- BZ - 107274 - Loss of IP tie-breaker vote not handled.
- BZ - 107276 - Disk tie-breaker thread started when IP tie-breaker in use
- BZ - 108148 - RFE: Implement statusIP in svclib_ip
- BZ - 109037 - Split brain occurs when cluster service is started while the NIC on one node is disconnected.
- BZ - 109958 - error message when adding IP service
- BZ - 110261 - allows IP address of the IP-based tie-breaker to be left empty
- BZ - 111934 - manpage incomplete
- BZ - 112300 - services do not failover after a member is disconnected from shared storage and reboots
CVEs
(none)
References
(none)
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.