RHBA-2013:1769 - Bug Fix Advisory

Topic

Updated glusterfs, python-keystoneclient, python-swiftclient, and samba packages
that fix numerous bugs and add various enhancements are now available for Red
Hat Storage 2.1.

Description

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

The updated Red Hat Storage Server packages include numerous bug fixes and
enhancements in Geo-replication. With this update, Quota is a fully supported
feature. It also introduces support for In-Service Rolling Upgrade, which
enables you to upgrade to the latest version without stopping the replicated and
distributed-replicated volumes. Space precludes documenting all of these changes
in this advisory. Users are directed to the Red Hat Storage 2.1 Technical Notes
for information on the most significant of these changes:

https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/2.1/html/Technical_Notes/index.html

Users of Red Hat Storage are advised to upgrade to these updated packages, which
fix these bugs and add these enhancements.

Solution

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

Affected Products

• Red Hat Enterprise Linux Server 6 x86_64
• Red Hat Enterprise Linux Server 5 x86_64
• Red Hat Gluster Storage Server for On-premise 2.1 x86_64
• Red Hat Storage for Public Cloud (via RHUI) 2.1 x86_64

Fixes

• BZ - 858434 - multiple entries in smb.conf
• BZ - 858494 - excessive logging in self-heal daemon should be reduced
• BZ - 871015 - quota: moving files between directories does not update the size field properly
• BZ - 875079 - Rebalance process crashed when geo-rep session was running.
• BZ - 876461 - quota: max limits getting crossed for directories
• BZ - 896444 - DHT : not able to move/rename directory, gives error -cannot move ` ' to a subdirectory of itself ' ', (all bricks where up, destination dir was present but it was empty)
• BZ - 908754 - Error messages are logged in geo-replication logs whenever a checkpoint is configured.
• BZ - 950314 - DHT - after adding brick/s, layout for root directory is getting changed (without running rebalance) so files created on mount point after adding bricks are distributed to new brick/sub-volume also
• BZ - 956276 - DHT - rebalance - If no. of 'subvols-per-directory' is less than no. of up sub-volumes then log of each rebalance run says 'found anomalies in <dir>. holes=#X overlaps=#Y'
• BZ - 961704 - are-equal check sum after rebalance giving error :Transport endpoint is not connected
• BZ - 977544 - gluster volume quota limit-usage now takes 40 seconds per command execution
• BZ - 978704 - quota: gluster volume status should provide info about quotad
• BZ - 980910 - Dist-geo-rep : Change in meta data of the files on master doesn't get propagated to slave.
• BZ - 981692 - quota: E [glusterd-utils.c:3674:glusterd_nodesvc_unlink_socket_file] 0-management: Failed to remove /var/run/5599c1d754915c52e215f7dd65d874a4.socket error: No such file or directory
• BZ - 982629 - quota: hitting "D" state for dd command
• BZ - 984603 - Dist-geo-rep : hardlinks to files are not synced as actual hardlinks by first xsync crawl.
• BZ - 985783 - quota+nfs : add-brick results in EIO
• BZ - 985812 - quota + remove-brick: remove brick fails to start
• BZ - 986948 - quota: limit crosses for symlink
• BZ - 987272 - Dist-geo-rep : geo-rep checkpoint works but takes utc time for start time and local time for finish time.
• BZ - 987292 - [RFE] Dist-geo-rep : Passive replica brick gets changelogs in .processing and processes all of them when it becomes active.
• BZ - 988275 - quota + afr: split brains on "ls"
• BZ - 989758 - 'gluster volume quota <volname> list' shows inconsistent output
• BZ - 991174 - Data Loss after Self Healing
• BZ - 996412 - Dist-geo-rep : when user starts geo rep session between master and slave cluster, default change_detector should be changelog not xsync
• BZ - 998786 - quota: list shows no information
• BZ - 998793 - quota: auxiliary mount should use some arbitrary name
• BZ - 998797 - quota: even after disabling quota the list still shows some information
• BZ - 998904 - quota: rename fails
• BZ - 998914 - quota: list shows different result on different nodes
• BZ - 998943 - Dist-geo-rep: logrotate utility command rotates the geo-replication log file but doesn't open a new one to write.
• BZ - 999269 - quota: alert message related to soft limit missing
• BZ - 999828 - quota: kernel compilation fails
• BZ - 1000302 - quota: list fails to display all the paths
• BZ - 1000903 - quota build: reset command fails
• BZ - 1000916 - quota build 2: linux untar goes to "D+" state, during rebalance
• BZ - 1000922 - Dist-geo-rep : geo-rep config log-level option takes invalid values and makes geo-rep status defunct
• BZ - 1000936 - Quota: With quota disabled, shouldn't incur overheads of accounting or enforcing quota
• BZ - 1000948 - Dist-geo-rep: Crawling + processing for 14 million pre-existing files take very long time
• BZ - 1000992 - quota build 3: list still shows large number for soft limit
• BZ - 1000996 - quota build 3: soft-limit "A" message is completely wrong
• BZ - 1001432 - quota build 3: glusterd.vol.log reports "E" messages
• BZ - 1001489 - Quota-build3: CLI crash while running "quota list" command
• BZ - 1001556 - quota: quota list command shows the used size incorrectly on every alternate command execution
• BZ - 1001631 - Quota: glusterfsd process crashed
• BZ - 1001893 - qemu-kvm segmentation fault while boot guest from glusterfs with wrong host name
• BZ - 1001899 - quota: default-soft-limit option does not seem to be working
• BZ - 1002022 - Change default rollover-time and fsync-interval for changelog
• BZ - 1002117 - quota build 3: mkdir and cp failed on a single brick volume
• BZ - 1002496 - [quota] All brick processes got killed, while removing the directory from fuse mount on which quota is set and recreating the same directory, followed by 'quota list'
• BZ - 1002530 - quota: directory quota limit crossed, if limit is changed while I/O is happening
• BZ - 1002613 - brick logs continuously reporting " I [socket.c:2237:socket_event_handler] 0-transport: disconnecting now"
• BZ - 1002885 - Quota limit violated upon creating a file after add-brick and fix-layout
• BZ - 1003549 - quota: deem-statfs on and df shows wrong value of limit set
• BZ - 1003736 - quota+rootsquash: unable to set limit on a non-root user directory if root-squash is on
• BZ - 1003757 - AFR: Mount crash lead to data corruption when a brick is down
• BZ - 1003759 - quota: setting limit on a single brick volume is not happening
• BZ - 1004235 - Dist-geo-rep: Both creates and deletes are not synced to slave after rpm upgrade from 2.0 to 2.1
• BZ - 1005460 - quota: "df -h" does not display an existing mount once deem-statfs is put to on
• BZ - 1005465 - quota: setting the soft/hard-timeout are reported in logs not on stdout
• BZ - 1005478 - Dist-geo-rep: 'geo-rep stop' should fail when there is a node down
• BZ - 1005483 - Dist-geo-rep: 'geo-rep' delete succeeds when there is a node down and when the node comes back up it has stale data
• BZ - 1005553 - Dist-geo-rep: glusterd crashed when started with -LDEBUG and ran geo-rep status detail
• BZ - 1006172 - Dist-geo-rep: Performance degradation between earlier versions to .33rhs
• BZ - 1007866 - sequential read performance not optimized for libgfapi
• BZ - 1008173 - Running a second gluster command from the same node clears locks held by the first gluster command, even before the first command has completed execution
• BZ - 1009851 - quota: exit code is set to "1" for list command
• BZ - 1010239 - nfs: nfs process crash when nfstest_posix tool is run.
• BZ - 1010248 - quota: Used field shows data in "PB" after deleting data from volume
• BZ - 1011905 - [Quota]: Input values to default-soft-limit option are not validated
• BZ - 1012711 - upgrading from RHS-2.0 causes 'kernel oplocks = no' to remain in /etc/samba/smb.conf.rpmnew
• BZ - 1012900 - [Quota]: Input values to limit-usage option are not validated properly
• BZ - 1013556 - [Quota]: The return value of `help' command should be 0
• BZ - 1014002 - geo-replication log message points to 2.0 Administration guide for geo-rep env setup instead of 2.1.
• BZ - 1016019 - Quota: Client inherits limit-usage value after disabling and enabling quota.
• BZ - 1016478 - quota: dir quota limit mismatches in calculation with actual amount of data in it
• BZ - 1016971 - glusterd: core dumped when quota enabled
• BZ - 1017007 - glusterd crash seen when volume operations are performed simultaneously on the same node, and one fails.
• BZ - 1019515 - geo-replication status for some nodes is continually "checkpoint as of <date_time> not reached yet"
• BZ - 1019806 - Quota + Rebalance : "Disk quota exceeded" warning message seen on file creation even after quota is disabled
• BZ - 1020886 - quota: quota-deem-statfs on and their is mismatch in the values shown by "df -h" and quota list command
• BZ - 1021492 - quota: Used space is non 0 after deletion of all files from the client
• BZ - 1021800 - quota: Input/output error with cp command
• BZ - 1021808 - gfapi - hang when heavily multithreaded app attempts parallel reads
• BZ - 1022518 - Dist-geo-rep : When node goes down and come back in master cluster, that particular session will be defunct.
• BZ - 1022582 - dist-geo-rep: Worker process crashing because of "Invalid Argument" error in slave
• BZ - 1023124 - optimize geo-replication changelog processing
• BZ - 1023382 - Dist-geo-rep : geo-rep went to faulty with traceback OSError: [Errno 22] Invalid argument: '.gfid/00000000-0000-0000-0000-000000000000'
• BZ - 1024496 - improve gfapi performance
• BZ - 1025163 - quota: list command fails with "Error on quota auxiliary mount"
• BZ - 1025205 - BVT: smb mount is failing for glusterfs.x86_64 0:3.4.0.37rhs-1.el6rhs
• BZ - 1025231 - Dist-geo-rep : geo-rep status goes to faulty with backtrace "failed on peer with KeyError 'stat'"
• BZ - 1025333 - quota: after reset command, and setting quota-deem-statfs to "on", df displays wrong values
• BZ - 1025358 - Dist-geo-rep: checkpoint says completed even before checkpoint is reached.
• BZ - 1025392 - dist-geo-rep : No way to reset or unset the checkpoint once set.
• BZ - 1025408 - dist-geo-rep : glusterd crashes while resetting the geo-rep config options
• BZ - 1025471 - CI tests are failing with "0-testvol-dht: (null): failed to get the 'linkto' xattr No data available" on clients.
• BZ - 1025476 - All glusterfsd processes crashed when one of the node went down two times in succession and while renames were happening
• BZ - 1025604 - nfs process crashed while running FS sanity on a glusterfs mount.
• BZ - 1025953 - Dist-geo-rep : slave's timestamp mark attr should be '*.stime'
• BZ - 1025954 - Dist-geo-rep : hybrid crawl does not sync symlinks (and error's out)
• BZ - 1025956 - Dist-geo-rep : 'stime' xattr is not the minimum of all distribute subvolumes
• BZ - 1025967 - RFE: dist-geo-rep: use tar+ssh as an option for data synchronization
• BZ - 1027137 - dist-geo-rep: After checkpoint if a node reboots, the status goes to faulty after it becomes online.
• BZ - 1027252 - Dist-geo-rep : gsyncd process crashed while removing files after remove brick on the master.
• BZ - 1027364 - Quota: Copying of data hangs with a kernel backtrace in /var/log/messages.
• BZ - 1027525 - quota: quota list and quota list <path> returns different information for same path
• BZ - 1027686 - Windows clients are not able to retrieve and not respecting ACLs on directories
• BZ - 1027687 - Quota: Difference in size reported by "df" and actual data within the directory.
• BZ - 1028002 - Home folder of Samba user is getting exposed through smb on fresh installs of rhs 2.1U1
• BZ - 1028299 - Dist-geo-rep : geo-rep is skipps all the changelogs and doesn't sync any files to slave.
• BZ - 1028343 - dist-geo-rep: delete operations results in a slave crash
• BZ - 1028675 - Dist-geo-rep : geo-rep checkpoint is broken, not shown in geo-rep status after checkpoint set.
• BZ - 1028732 - dist-geo-rep: glusterd crashed while running geo-rep status detail
• BZ - 1029300 - Red Hat Storage Server installation from RH Satellite Server fails, due to missing dependency packages, and package conflict issues
• BZ - 1029575 - Dist-geo-rep: use-tarssh option takes even garbage value and returns success
• BZ - 1029577 - dist-geo-rep: It should be logged in the geo-rep logs, when gsync is using tar+ssh as syncing method

CVEs

(none)

References

• https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/2.1/html/Technical_Notes/chap-Documentation-Technical_Notes-rhs_update1.html