RHBA-2013:1064 - Bug Fix Advisory

Topic

Updated glusterfs, vdsm, gluster-swift, appliance, and rhs-c packages that fix
several bugs are now available for Red Hat Storage 2.0.

Description

Red Hat Storage is software only, scale-out storage that provides flexible and
affordable unstructured data storage for the enterprise.

Bug Fixes:

• The format of the internal key used to identify a fully qualified domain name

(FQDN) based hostname was not complied by the parser and the NFS mounts failed
when a client with FQDN based hostname was mounted. This issue is now fixed to
comply with the parser and the NFS mount works.(BZ#906119)

• The option to disable root-squash was not executed properly in server protocol

module and root-squash could not be disabled when the volume was up. Now, the
option to disable the root-squash is executed in the server-protocol and RPC
layer and an administrator can disable root-squash while the volume is
up.(BZ#964032)

• When a volume is enabled with root-squash, all the internal/trusted clients

must be allowed to bypass the root-squash check. Daemons such as self-heal are
passed through root-squash check. Now, there is a mechanism to distinguish the
clients which are trusted and root-squash check is not performed on those client
processes.(BZ#961492)

• In quick-read translator, the uid/gid of a user was not copied correctly to

the filesystem operations made to the server, thus enabling root-squash on those
operations. Non-root users who did not fall under root-squash were also treated
as nobody:nobody, thus breaking the POSIX-compliance.This issue is now fixed and
the root-squash behavior is consistent with the standards.(BZ#961491)

• glusterd init/service scripts did not create a lockfile while starting the

process. Hence, during a reboot, glusterd process was not stopped automatically.
Now, locking and unlocking mechanism have been added in glusterd init script and
during reboot, glusterd service stops properly. (BZ#958666)

• The VDSM in Red Hat Storage 2.0 Update 4 node had Secure Sockets Layer (SSL)

enabled but was set to false for communication in the Red Hat Storage Console.
Hence, add server failed with a SocketException error. Now, the VDSM is
configured to false. After installing VDSM, stop, reconfigure and start the VDSM
service to successfully add a server in the Red Hat Storage Console.(BZ#928311)

• VDSM in Red Hat Storage 2.0 Update 4 node reported cluster compatibility level

3.1/3.2 while the Red Hat Storage Console required compatibility level 2.0.
Hence, a Red Hat Storage 2.0 Update 4 node could not be added using the Red Hat
Storage Console.The VDSM was modified to support cluster compatibility level
2.0. Now, adding a Red Hat Storage 2.0 Update 4 node using the Red Hat Storage
Console is successful.(BZ#924193)

• The Jboss EAP version available in channel has been updated to 6.1 from 6.0.

Hence, Red Hat Storage Console installation fails. Now, the setup scripts is
updated to reflect the correct location of Jboss files needed during
installation and the installation is successful.(BZ#966864)

• While adding a Red Hat Storage Update 4 node to Red Hat Storage Console,

vdsm-gluster package failed to install due to an error in the Gluster Package
Bootstrap component of VDSM. Now, the VDSM bootstrap component is modified and
adding a Red Hat Storage node is successful.(BZ#963676)

• Changelogs in synchronous replication could become incorrect following an

ungraceful shutdown of xfs resulting in files not being self-healed or let
unreliable self-heal happen, which can lead to potential data corruption. The
process of updating changelogs has been made resilient to avoid this
inconsistency.(BZ#973922)

• Installing or upgrading the gluster-swift-plugin RPM overwrites /etc/swift

configuration files. Hence, the customer configuration is overwritten, causing
data unavailability. Now, the RPM installs or upgrades new configuration files
with a non-conflicting extension and customer configuration files are not
overwritten, maintaining data availability.(BZ#969224)

Solution

Before applying this update, make sure all previously-released errata
relevant to your system have been applied.

This update is available via the Red Hat Network. Details on how to
use the Red Hat Network to apply this update are available at
https://access.redhat.com/knowledge/articles/11258

Affected Products

• Red Hat Gluster Storage Server for On-premise 2.0 x86_64
• Red Hat Storage for Public Cloud (via RHUI) 2.0 x86_64
• Red Hat Gluster Storage Management Console (for RHEL Server) 2.0 x86_64

Fixes

• BZ - 924193 - [RHS-C] Unable to add the latest RHS 2.0+ host in RHS-C due to compatibility issues
• BZ - 963676 - [RHSC] Add host failure (RHS Anshi node to rhsc-2.0.techpreview1-4.el6rhs.noarch)
• BZ - 964032 - root-squash: root-squashing does not get disabled dynamically
• BZ - 966864 - The latest rhsc-setup fails
• BZ - 977250 - running dbench results in leaked fds leading to OOM killer killing glusterfsd.
• BZ - 978802 - Client crashed on hypervisor after rebalance on a distributed-replicate volume

CVEs

(none)

References

(none)