RHBA-2005:753 - Bug Fix Advisory

Topic

An updated system-config-cluster package that provides various bug fixes is
now available.

Description

BIND (Berkeley Internet Name Domain) is an implementation of the DNS
(Domain Name System) protocols. BIND includes a DNS server (named), which
resolves host names to IP addresses; a resolver library (routines for
applications to use when interfacing with DNS); and tools for verifying
that the DNS server is operating properly.

This erratum addresses the following bugs:

• When Failover Domains are removed, services that used the Domain are now

updated.

• GNBD fence parameters have been updated.
• Editing of existing gnbd fences now works and saves correctly.
• Traceback has been fixed when closing the fence config window without

fence devices configured.

• Creating fence devices in a multicast cman cluster now correctly locates

the fence device under the method tag, rather than the multicast tag.

• Cluster.ng errors were corrected
• The cluster icon now correctly appears in the desktop navigator menu.
• This erratum includes validation that prevents cluster nodes and fence

devices from having the same name. Similar names defeat an important
section of the cluster.ng file.

• A problem with specifying manual fencing has been addressed.
• Removing the cluster.conf file from underneath a running s-c-cluster

application no longer generates a traceback.

• Now when 'send to cluster' is clicked, the gui 'modified' flag is

removed.

• Cluster management window now refreshes immediately if any change is

made.

• Modifications to defined services, of any sort, no longer generate

tracebacks.

• The node table is now repopulated immediately after moving a service.
• The 'gfs_name' string error has been fixed.
• force_unmount can now be set for file systems
• Autostart is no longer always set when loading a service for editing.

All users of bind should upgrade to this updated package, which resolves
these issues.

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.

Affected Products

• Red Hat Enterprise Linux High Availability for x86_64 4 x86_64
• Red Hat Enterprise Linux High Availability for x86_64 4 ia64
• Red Hat Enterprise Linux High Availability for x86_64 4 i386

Fixes

• BZ - 159965 - Cluster Management window does not refresh after configuration change and traceback
• BZ - 160127 - Clicking "Send to Cluster" does not clear "modified" indicator from "Current File Name" box
• BZ - 160240 - removing /etc/cluster out from under the GUI will cause a traceback when saving
• BZ - 160264 - garbage cluster.conf files cause the GUI to die at startup
• BZ - 161344 - GUI fails to start with valid conf file: error in in resolve_fence_instance_types
• BZ - 161974 - creates borken fence_manual configuration
• BZ - 163237 - GUI allows cluster node and fence device to have the same name
• BZ - 163673 - Icon path in system-config-cluster dekstop file is wrong
• BZ - 164407 - system-config-cluster generates poorly formed XML in cluster.conf
• BZ - 164857 - redhat-config-cluster does not show nodes after transfering services between nodes
• BZ - 164936 - traceback when attempting to edit a gnbd fence device
• BZ - 165130 - Fence levels are created under <multicast> tag
• BZ - 165140 - Traceback when fencing cluster node and no fence device exists
• BZ - 165169 - GNBD fence configuration is broken
• BZ - 165184 - Removal of Failover Domain doesn't update Services
• BZ - 166140 - system-config-cluster doesn't allow force_unmount to be set for FS
• BZ - 166663 - global name 'gfs_name' is not defined when editing a filesystem resource
• BZ - 167429 - Autostart of a service gets automatically set

CVEs

(none)

References

(none)