RHEA-2014:1278 - Product Enhancement Advisory

Topic

Red Hat Storage Server packages namely glusterfs, gluster-nagios-addons,
gluster-nagios-common, nrpe, nsca, nagios-plugins,gluster-swift,
nfs-ganesha,ctdb-2.5 packages that fix numerous bugs and add various
enhancements are now available for Red Hat Storage 3.0.

Description

Red Hat Storage is a software only scale-out storage solution that
provides flexible and affordable unstructured data storage. Red Hat
Storage 3.0 unifies data storage and infrastructure, increases
performance, and improves availability and manageability to meet
enterprise-level storage challenges.

This update fixes numerous bugs and adds various enhancements in
Geo-replication, DHT, CTDB, NFS, SMB. Space precludes documenting
all of these changes in this advisory. Users are directed to the
Red Hat Storage 3 Technical Notes, linked to in the References section,
for information on the most significant of these changes.

This advisory also adds the following new features:

• Monitoring of Red Hat Storage servers is built on Nagios platform

to monitor Red Hat Storage trusted storage pool, hosts, volumes, and
services. You can monitor utilization, status, alerts and notifications
for status and utilization changes.(BZ#1063923)

• Red Hat Storage Snapshot feature enables you to create point-in-time

copies of Red Hat Storage volumes, which you can use to protect data.
Users can directly access Snapshot copies which are read-only to
recover from accidental deletion, corruption, or modification of
the data. (BZ#891352)

• The log management framework generates log messages for each of the

administrative functionalities and the components to increase the
user-serviceability aspect of Red Hat Storage Server. Logs are
generated to track the event changes in the system. The feature
makes the retrieval, rollover, and archival of log files easier
and helps in troubleshooting errors that are user-resolvable with
the help of the Red Hat Storage Error Message Guide. (BZ#1096565)

All users of Red Hat Storage are advised to install these updated packages.

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/site/articles/11258

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 3 for RHEL 6 x86_64
• Red Hat Gluster Storage Management Console (for RHEL Server) 3 x86_64
• Red Hat Gluster Storage Nagios Server 3 for RHEL 6 x86_64

Fixes

• BZ - 948234 - fuse: logs display zero gfid
• BZ - 951488 - DHT - rebalance - gluster volume rebalance <volname> status shows output even though User hasn't run rebalance on that volume (it shows remove-brick status)
• BZ - 964164 - gluster volume status output shows rebalance as running, though the rebalance status output shows the tasks as completed
• BZ - 969298 - Renaming file while rebalance is in progress causes data loss
• BZ - 969993 - nfs: help does not display performance.nfs.* options
• BZ - 970686 - DHT :- not able to unlink file ( rm -f, unlink) if cached sub-volume is up and hashed sub-volume is down
• BZ - 976902 - gluster peer detach force should fail if the peer has bricks as part of a distributed volume
• BZ - 1002822 - Dist-geo-rep : volume won't be able to stop untill the geo-rep session is deleted.
• BZ - 1003914 - remove-brick :- If User executes 'gluster volume remove-brick <vol> <brick> commit' command before 'gluster volume remove-brick <vol> <brick> start' commands; it removes brick and ends in data loss
• BZ - 1006729 - Dist-geo-rep : first xsync crawl failed to get the meta data changes made to directories.
• BZ - 1006772 - nfs: some vague message in logs
• BZ - 1006809 - DHT: Kernel untar fails on the mount point after add-brick
• BZ - 1007033 - Excessive logging of warning message "remote operation failed: No data available" in samba-vfs logfile
• BZ - 1018043 - Crash in glusterd when command issued from multiple peers simultaneously
• BZ - 1024459 - Unable to create hardlinks when the source and destination are in the same directory.
• BZ - 1026227 - quota: volume stop leaves the volume mount with "Transport endpoint is not connected"
• BZ - 1026787 - dist-geo-rep: geo-rep create no longer throws warning message when the slave has less available size than master
• BZ - 1028878 - "volume status" for single brick fails if brick is not on the server where peer command was issued.
• BZ - 1029444 - Able to set and get "trusted.glusterfs.volume-id" extended attribute from mount point
• BZ - 1030052 - dist-geo-rep: When use-tarssh is set to "true" when it is already using tar+ssh, gsyncd still restarts
• BZ - 1030393 - dist-geo-rep: Worker crashing with "ValueError: filedescriptor out of range in select()" backtrace in logs
• BZ - 1030432 - quota: after quota remove command and still quota-deem-statfs on the df -h shows the "size" field shows lower value
• BZ - 1035042 - Despite glusterd init script now starting before netfs, netfs fails to mount localhost glusterfs shares in RHS 2.1
• BZ - 1038973 - [SNAPSHOT] : Snapshot create command failed
• BZ - 1038990 - [SNAPSHOT] : glusterd crash while creating snapshot
• BZ - 1038994 - Dist-geo-rep : geo-rep worker of the passive node crashed when it became active.
• BZ - 1039569 - [Functional] Object Expirer doesn't clean up objects yet it accepts headers X-Delete-After & X-Delete-At
• BZ - 1039956 - [SNAPSHOT] : For the same snap, Snap ID listed is different on different nodes
• BZ - 1040934 - [SNAPSHOT] : Snap volume is not read only
• BZ - 1040947 - [SNAPSHOT] : Snapshot list output displays "Volume <snap_name> Does not exist" which is confusing
• BZ - 1040978 - [SNAPSHOT]:Need clearer messages while creating SNAP with invalid scenaios
• BZ - 1042747 - [SNAPSHOT] : CLI crash while creating CG with description more than 1024C and the CG was not created
• BZ - 1042821 - [SNAPSHOT]: Listing snapshot in detail ( -d ) option does not give all the details
• BZ - 1043472 - [SNAPSHOT] : snapshot cli tree structure is not present as part of the "gluster help"
• BZ - 1043566 - Updating glusterfs packages reads 'rpmsave' files created by previous updates, and saves the files as <file>.rpmsave.rpmsave.
• BZ - 1043792 - [SNAPSHOT] : snapshot create without snap name shows ??? in the returned output
• BZ - 1043862 - [SNAPSHOT] : glusterd crashed while acquiring volume lock when the snap create command is executed on the same vol from all the nodes in cluster
• BZ - 1044420 - dist-geo-rep: Python backtrace seen in geo-rep logs "ValueError: signal only works in main thread"
• BZ - 1044476 - [SNAPSHOT]: gluster snapshot list does not show any snaps taken on the volume after restarting glusterd
• BZ - 1044867 - [SNAPSHOT]: once all the gluster process are killed and restarted, the snapshot list for a volume shows double of the snaps taken
• BZ - 1045305 - [SNAPSHOT] : snap create command returned failure for snap names starts with -, but snap is listed on local host
• BZ - 1045333 - [SNAPSHOT] : Snap creation fails when volumes contain "-" ex: vol-snap
• BZ - 1046908 - [Rebalance]:on restarting glusterd, the completed rebalance is starting again on that node
• BZ - 1048126 - [SNAPSHOT]: gluster snapshot delete with wrong options gives usage but mentions command as gluster remove
• BZ - 1048138 - [SNAPSHOT]: gluster volume delete <snapvolume> should have clear message to use "gluster snapshot delete"
• BZ - 1048149 - [SNAPSHOT]: glusterd logs are filled with "Request received from non-privileged port. Failing request" while deleting snaps in a loop
• BZ - 1048216 - [SNAPSHOT]: No warning message displayed to User on deleting Snapshot
• BZ - 1048749 - nfs: while using the option nfs.rpc-auth-reject, a volume mount fails but a subdirectory mount still is successful
• BZ - 1048831 - [SNAPSHOT]: brick process crashed while creating snapshot when multiple file/directory creation is inprogress from fuse and nfs mount
• BZ - 1048840 - [SNAPSHOT]: glusterd crashed while creating snapshot when multiple file/directory creation is inprogress from fuse and nfs mount
• BZ - 1049171 - [SNAPSHOT]: glusterd crashed while taking volume status with pthread_spin_lock () from /lib64/libpthread.so.0
• BZ - 1049187 - [SNAPSHOT]: Clean up required on the node where glusterd was down while deleting snapshot
• BZ - 1049240 - [SNAPSHOT]: volume lock: once a lock is being taken and for some reason its not released, than the lock is held forever
• BZ - 1049278 - [SNAPSHOT]: glusterd crashed while performing IO and taking snapshot at the same time
• BZ - 1049353 - [SNAPSHOT]: Snapshot delete failed
• BZ - 1049370 - [SNAPSHOT]: Need modification in message while deleting non existant snap
• BZ - 1049834 - [SNAPSHOT]: Currently it is allowed to create any number of snapshots for a volume, it should be 256 max
• BZ - 1049857 - [SNAPSHOT]: Snap creation fails when the snap name is very long
• BZ - 1054151 - [SNAPSHOT]: Snapshot list shows epoch time on the nodes after glusterd restart
• BZ - 1054168 - [SNAPSHOT]: Snapshot name creation fails when snap name starts with "-"
• BZ - 1054705 - [SNAPSHOT]: snap creation fails when used the same name for different volumes
• BZ - 1056550 - Dist-geo-rep : after hardlink syncing to slave, arequal on slave mount failed with short read for some files.
• BZ - 1056995 - SMB:Multiple mount point with different VIP's hangs when one of the node is rebooted in the ctdb cluster.
• BZ - 1058260 - [SNAPSHOT]: OOM: lvcreate invoked oom when tiobench was inprogress from fuse and nfs mount
• BZ - 1058272 - [SNAPSHOT]: glusterd crashed while executing volume status from all nodes
• BZ - 1059146 - [SNAPSHOT] : Tracker bug for snapshot performance degradation from snap1 to snap256
• BZ - 1061580 - mount hangs, when all the bricks in replica group go down while writes are in progress
• BZ - 1062158 - AFR : self-heal-daemon not clearing the change-logs of all the sources after self-heal
• BZ - 1063775 - [SNAPSHOT]: Need modification in message while restoring a volume which is in the 'started' state to a particular snap
• BZ - 1064325 - [SNAPSHOT]: After restoring volume , status of volume is shown as 'stopped' and fuse mount of the volume is possible
• BZ - 1064688 - [SNAPSHOT]: Creating files after restoring volume gives "Read only filesystem "error
• BZ - 1064744 - [SNAPSHOT]: Unable to start volume after restoring it
• BZ - 1064768 - glusterd hangs when volume profile start command is executed
• BZ - 1065344 - [SNAPSHOT] : Snap Volume brick crash while creating snapshots when compile kernel was in progress
• BZ - 1065953 - [SNAPSHOT]: Once the volume is restored the client doesnt get notification for the changes in volume file and it fails "Transport EndPoint not connected"
• BZ - 1065956 - [SNAPSHOT]: Once the volume is restored the nfs client fails "stale file handle" until its not remounted
• BZ - 1066260 - [SNAPSHOT] : Need modification in message while restoring to non existing snap/volume
• BZ - 1066389 - [AFR] I/O fails when one of the replica nodes go down
• BZ - 1067342 - [SNAPSHOT]: Restore is successful even when peer glusterd/nodes are down.
• BZ - 1071377 - [NeedInfo] volume creation fails with "brick path is too long" in weird circumstances
• BZ - 1072253 - [SNAPSHOT]: After gluster installation glusterd fail to start when glusterd is started manually
• BZ - 1075034 - [SNAPSHOT]: snap-max-hard-limit and snap-max-soft-limit should be allowed to set in the same CLI
• BZ - 1075446 - [SNAPSHOT]: Output correction in snapshot info and create
• BZ - 1075454 - [SNAPSHOT]: snapshot info output is ambiguous
• BZ - 1075512 - [SNAPSHOT]: snapshot create failed when the snap names are l,r,i,d
• BZ - 1075527 - [SNAPSHOT]: glusterd crashed while giving the wrong path to mount the snap volume
• BZ - 1075988 - [SNAPSHOT]: glusterd crashed when the snap name provided was very long
• BZ - 1076127 - Yum update/install of RHS3.0 qa build is failing on top of RHS2.1U2GA ISO
• BZ - 1076356 - [SNAPSHOT]: Segmentation fault reported on gluster snapshot create
• BZ - 1077142 - [SNAPSHOT]: snapshot list and info is broken after snap restore.
• BZ - 1077196 - [SNAPSHOT]: Snap/Volume lock issue after restoring the volume to its snapshot
• BZ - 1077646 - Dist-geo-rep : geo-rep status fails to get status from peers.
• BZ - 1077655 - [SNAPSHOT]:Volume deletion successful when the snapshots of the volume are still present
• BZ - 1078166 - [SNAPSHOT]: Correction required in error message while creating snap with name longer than 255 characters
• BZ - 1080245 - The child directory created within parent directory ( on which the quota is set ) shows the entire volume size, when checked with "df" command.
• BZ - 1080763 - SMB:samba and ctdb hook scripts are not present in corresponding location after installation of 3.0 rpm's
• BZ - 1081899 - "glusterd" service does not start automatically after reboots
• BZ - 1081989 - [SNAPSHOT]: Creating a new snapshot with an existing snap name fails first time but is successful the next time and the Snap UUID and the Snap Volume changes
• BZ - 1082043 - [SNAPSHOT]: gluster snapshot status timesout without displaying the output when snaps are >150
• BZ - 1082678 - Request to update graphics for Red Hat Storage Server 3
• BZ - 1082951 - [SNAPSHOT]: Snapshot config set is not updated on a node which had glusterd offline and than rebooted
• BZ - 1083014 - [SNAPSHOT]: setting the soft limit to greater than 100% displays that "Invalid snap-max-soft-limit 0"
• BZ - 1083020 - [SNAPSHOT]: Setting the config value to alphanumeric values should not be allowed.
• BZ - 1083267 - SMB: FS sanity on cifs mount is failing with OOM : kill process glusterfsd
• BZ - 1083449 - [SNAPSHOT]: glusterfsd crashed while stopping the volume during IO from client
• BZ - 1083502 - [SNAPSHOT]: snapshot create when one of the brick is down should output the proper message
• BZ - 1083668 - BVT: profile tests hang because of Gluster issues
• BZ - 1083709 - Perf: OOM when running performance regression tests(iozone sequential writes)
• BZ - 1083852 - BVT: glusterfs-server-3.5qa2-0.304.git0c1d78f installation is failing
• BZ - 1083879 - [SNAPSHOT]: Able to create the snapshots beyond "effective snap-max-hard-limit"
• BZ - 1083882 - [SNAPSHOT]: snapshot config <vol> is to list the config, it should not acquire the volume lock to list.
• BZ - 1083917 - [SNAPSHOT]: "Assertion failed: volname" while doing the system config change when snap create was in progress
• BZ - 1084014 - [SNAPSHOT] : brick crash while creating snapshot on volume where rebalance was completed
• BZ - 1084409 - [SNAPSHOT]: Output correction in gluster snapshot config snap-max-soft-limit
• BZ - 1084413 - [SNAPSHOT]: gluster snapshot config should only accept the decimal numeric value
• BZ - 1084496 - [SNAPSHOT] : Post Validation failed error message while creating snapshots
• BZ - 1084892 - [RFE] Log when quorum not available
• BZ - 1084897 - [SNAPSHOT]:bricks crashed while rebalance was running and rebalance status was checked at the same time
• BZ - 1084906 - [SNAPSHOT]: glusterfsd crashed while taking snapshots when selfheal was in progress
• BZ - 1084926 - [SNAPSHOT]: version is reset to 1 after restore
• BZ - 1084958 - SMB: CIFS mount fails with the latest glusterfs rpm's
• BZ - 1084982 - [SNAPSHOT] : Need modification in message while creating snapshot
• BZ - 1085254 - Quota: Soft limit crosed alert not logged in brick or syslogs
• BZ - 1085278 - [SNAPSHOT]: After adding a new peer to the cluster, gluster snasphot create ,delete ,restore gives Post Validation error message
• BZ - 1085695 - RHS Samba packages dependency errors while doing yum update because of different version of samba in RHEL6.5
• BZ - 1086145 - [SNAPSHOT]: Stale entries of snapshots needs to be cleaned from /var/run/gluster/snaps/
• BZ - 1086511 - [RFE][RHS] Provide cloud-init package into RHS Cloud Access AMI
• BZ - 1086827 - CTDB hooks script adds bad entry in /etc/fstab
• BZ - 1087563 - SMB: Crash on brick process during compile kernel.
• BZ - 1088355 - [SNAPSHOT] : glusterd crash on 2 nodes while snapshot was in progress when IO was in progress on the client
• BZ - 1089527 - [SNAPSHOT]: Able to create snapshot when one of the brick is down even without force
• BZ - 1089620 - [SNAPSHOT]: Restarting glusterd fails after snapshots are taken on volume
• BZ - 1089664 - SMB: Windows client is not able to access gluster volume via SMB
• BZ - 1090621 - BVT: glusterfsd crashed while running Bonnie++ on cifs mount
• BZ - 1090837 - [SNAPSHOT]: glusterd crashed while deleting snaps in a loop
• BZ - 1090986 - DHT + Snapshot :- If snapshot is taken when Directory is created only on hashed sub-vol; On restoring that snapshot Directory is not listed on mount point and lookup on parent is not healing
• BZ - 1091921 - Add volume set options to enable/disable nfs-ganesha support
• BZ - 1091986 - We need a command to bump-up the glusterd op-version.
• BZ - 1092429 - Two instances each, of brick processes, glusterfs-nfs and quotad seen after glusterd restart
• BZ - 1092501 - DHT + Snapshot :- If snapshot is taken when Directory is not removed from hashed sub-vol; On restoring that snapshot Directory is not listed on mount point and lookup on parent is not healing
• BZ - 1094168 - dist-geo-rep: Geo-rep is broken in new build "glusterfs-3.5qa2-0.425.git9360107"
• BZ - 1094608 - Peer is disconnected and reconnected every 30 seconds
• BZ - 1094681 - [RHS-LOGGING DHT] :gf_log usage in DHT should be converted to gf_msg in order to test new logging framework
• BZ - 1094690 - [RHS-LOGGING] : can't test suppression feature as all gf_logs should be replaced by gf_msg
• BZ - 1094714 - [SNAPSHOT]: snapshot creation fails but df -h shows the snapshot brick as mounted
• BZ - 1094716 - Upgrade: glusterd crashes when a peer detach force is executed from 2.1 (The detached machine is on 3.0)
• BZ - 1094748 - Blocked with Snapshot dependencies testing with afr since some AFR patches not merged in master branch
• BZ - 1095267 - glusterfsd crashed when quota was enabled, then disabled and enabled again
• BZ - 1095671 - dist-geo-rep: while doing rm -rf on master mount, slave glusterfs crashed in io-cache.
• BZ - 1095686 - When a brick is brought down, after a while it comes online automatically.
• BZ - 1096139 - [SNAPSHOT]: Delete is successful and device is not present but df -h lists it
• BZ - 1096173 - CTDB: ctdb setup fails to come up and node remains unhealthy with older version of CTDB and RHS3.0
• BZ - 1096230 - dist-geo-rep: gsyncd worker crashing continuously when geo-rep start is executed.
• BZ - 1096476 - [SNAPSHOT]: Unable to stop volume after trying to restore the volume when the volume is started and one of the bricks goes offline
• BZ - 1096614 - readdir-ahead needs to be enabled by default for new volumes on rhs-3.0
• BZ - 1096966 - [RHS]add swiftonfile package
• BZ - 1097102 - glusterfsd crashes while doing stress tests
• BZ - 1097512 - "heal info" shows status of brick as "Success" for "Transport End Point Not Connected"
• BZ - 1097679 - missing small-file-perf file from /var/lib/glusterd/groups directory
• BZ - 1097782 - In-service software upgrade not throwing error, when glusterd, glusterfs, glusterfsd processes are still running
• BZ - 1098087 - [SNAPSHOT]: Snapshot restore fails if quota.conf is present and quota.cksum is not present
• BZ - 1098196 - [SNAPSHOT] : restoring a snapshot is setting the "features.barrier" option to "enable"
• BZ - 1098867 - Changelog: Draining and explicit rollover of changelog journal for geo-rep to work with snapshots.
• BZ - 1098971 - [REBALANCE] glusterfs rebalance process core dumps while rebalancing deep directory structure
• BZ - 1099010 - Dist-geo-rep : geo-rep create push-pem fails to push pem keys to slaves and consequently fails to setup geo-rep.
• BZ - 1099079 - cluster/afr: move messages to new logging framework
• BZ - 1099385 - RHS-3.0 op-versions need to be fixed
• BZ - 1099409 - With glusterfs update to the latest version the existing hook scripts are not saved as rpm save.
• BZ - 1099833 - [SNAPSHOT]: glusterd crashed while running snapshot creation for all the volumes while arequal was in progress
• BZ - 1100211 - [SNAPSHOT] : A brick volume-id is changed after reboot of the brick's node
• BZ - 1100282 - [SNAPSHOT]: cleanup of stale snap volume doesnt happen after missed restore and gluster cli's hungs
• BZ - 1100567 - [barrier] reconfiguration of barrier time out does not work
• BZ - 1100568 - [barrier] O_SYNC writes from libgfapi are not barriered
• BZ - 1100571 - [barrier] fsync on NFS mount was not barriered, when barrier was enabled
• BZ - 1101407 - [RFE] Dist-geo-rep : geo-rep pause won't retain state after the reboot or restart of the worker process.
• BZ - 1101514 - [SNAPSHOT]: Able to delete/restore even when glusterd quorum doesnt meet
• BZ - 1101588 - BVT: Volume top command for a wrong brick is causing cli to hang
• BZ - 1101910 - Dist-geo-rep: If the user is created without primary group in mount-broker setup, geo-rep fails to set proper ownership of .ssh and authorized keys.
• BZ - 1102550 - Dist-geo-rep : geo-rep failed to sync some files, with error "(Operation not permitted)" on slaves.
• BZ - 1102700 - [RHS]Install of RHSS from ISO issues warning about missing dependencies or package conflicts
• BZ - 1102747 - Dist-geo-rep : some of the files not accessible on slave after the geo-rep sync from master to slave.
• BZ - 1103155 - Perf regression with Denali
• BZ - 1103264 - vdsm fails to start at boot in freshly installed RHSS 3.0
• BZ - 1103275 - ctdb configured to start at boot, and fails to start, following fresh install of RHSS 3.0
• BZ - 1103680 - [SNAPSHOT]: Snapshot create deletes all the snapshots until it reaches the soft limit after the system config is changed
• BZ - 1103688 - quota: setting the limit fails
• BZ - 1104016 - hooks/nfs-ganesha: Disable ACL by default while starting nfs-ganesha.
• BZ - 1104121 - Dist-geo-rep: In geo-rep mount-broker setup, status shows "Config Corrupted" when status is requested without master and slave url.
• BZ - 1104153 - Dist-geo-rep : geo-rep history crawl consumes even zero-byte changelogs and accumulates in .history/.processed directory of working_dir
• BZ - 1104159 - Disable "volume heal" command's new option "statistics" for the denali release
• BZ - 1104574 - NEW - smb process starts, when user.smb option is set to disable.
• BZ - 1104602 - [SNAPSHOT]: op-version is incremented to 4 when a snapshot is created
• BZ - 1105102 - CTDB:Adding volume set option in hook script causes delay in glusterd operations.
• BZ - 1106428 - [RHS]RHS 3.0 ISO menu title is obsolete
• BZ - 1106442 - CTDB:CTDB fails to start because it does not find ctdb.conf file
• BZ - 1107575 - [SNAPSHOT]: Restoring snapshot to a volume fails with "Commit failed on <peer_node_name>", when glusterd is restarted after creation of the snapshot
• BZ - 1107665 - Dist-geo-rep : Glusterd crashed while resetting use-tarssh config option in geo-rep.
• BZ - 1108018 - peers go into `Peer Rejected' state while doing rolling upgrade
• BZ - 1108484 - CTDB upgrade: While doing RHS 3.0 upgrade excluding CTDB it fails with dependency issue
• BZ - 1108505 - quota:peer probe fails after adding the new node to the existing cluster with quota enabled
• BZ - 1108570 - RHS3.0: glusterd crash when detaching a node from existing cluster with peer detach command
• BZ - 1108588 - Dist-geo-rep : geo-rep fails to do first history crawl after the volume restored from snap.
• BZ - 1108589 - [SNAPSHOT]: After restore client-op-version of volume is reset to 0 which doesnt allow to mount on client
• BZ - 1108652 - [SNAPSHOT]: Restore fails with prevalidation when the glusterd is restarted after the quorum didnt match
• BZ - 1109020 - New component 'nagios'
• BZ - 1109141 - [SNAPSHOT]: Fails to mount missed snapshot
• BZ - 1109149 - Dist-geo-rep : snapshot with geo-rep, while creating files on master, resulted in failure to capture few files entry in changelogs.
• BZ - 1109557 - Dist-geo-rep : after renames on master, slave has more number files than master when synced through history crawl.
• BZ - 1109795 - [changelog] While doing IO's on fuse mount, changelog disable fails all the IO's
• BZ - 1110311 - BVT: Rebalance status reporting failure
• BZ - 1110694 - [DHT:REBALANCE]: Rebalance failures are seen with error message " remote operation failed: File exists"
• BZ - 1111122 - Dist-geo-rep : After upgrade, geo-rep crashes in gf_history_changelog.
• BZ - 1111148 - [SNAPSHOT]: Clear message is required when attempting to delete non-existing snap
• BZ - 1111171 - Dist-geo-rep : geo-rep xsync crawl takes too much time to sync meta data changes.
• BZ - 1111577 - Dist-geo-rep : geo-rep syncs files through hybrid crawl after history crawl is finished even though changelogs are available.
• BZ - 1111612 - [SNAPSHOT]: Temporary folders are created after snapshot create
• BZ - 1112582 - Dist-geo-rep : worker was not restarted by monitor, after it died, and remained in zombie state.
• BZ - 1113471 - Dist-geo-rep : first crawl will be history crawl even though change_detector is xsync.
• BZ - 1113852 - [SNAPSHOT]: In mixed cluster with RHS 2.1 U2 & RHS 3.0, snapshot commands should fail with proper error instead of "Another Transaction in progress"
• BZ - 1113961 - [SNAPSHOT] : Restoring the snap-volume once the volume is already restored results in a failure.
• BZ - 1115267 - 'warning: %post(glusterfs-3.6.0.22-1.el7.x86_64) scriptlet failed, exit status 2' on installing RHS client packages on RHEL 7
• BZ - 1115428 - [DHT-REBALANCE]: Few files are missing after add-brick and rebalance
• BZ - 1116761 - core: all brick processes crash when quota is enabled
• BZ - 1116789 - coredump files getting collected in "/" not in /var/log/core
• BZ - 1117135 - DHT :- data loss - file is missing on renaming same file from multiple client at same time
• BZ - 1117283 - DHT :- rm -rf is not removing stale link file and because of that unable to create file having same name as stale link file
• BZ - 1117286 - Layered install of RHSS 3.0 on RHEL 6 fails due to package dependency issues
• BZ - 1117421 - Upgrade from RHSS 2.1 to RHSS 3.0 fails with "Error: Trying to remove "ctdb", which is protected"
• BZ - 1119223 - [glusterd] glusterd crashed when it failed to create geo-rep status file.
• BZ - 1119739 - [Dist-geo-rep] In mount-broker setup, after geo-rep stop, status shows faulty instead of stopped.
• BZ - 1120198 - Peers moved to rejected state because of mismatch in volume checksums after creating the volume.
• BZ - 1120456 - rebalance is not resulting in the hash layout changes being available to nfs client
• BZ - 1120830 - [EARLY ACCESS] confusing error message when attempting to snapshot thick logical volumes
• BZ - 1121059 - [Dist-geo-rep] : In a cascaded setup, after hardlink sync, slave level 2 volume has sticky bit files found on mount-point.
• BZ - 1121099 - DHT: Accessing a directory fails with ENOENT on nfs mount after add-brick
• BZ - 1121603 - [SNAPSHOT]: man or info page of gluster needs to be updated with snapshot commands
• BZ - 1122502 - [Dist-geo-rep] : after changelog disable during geo-rep, if worker restarts it keeps crashing with "AttributeError: '_GMaster' object has no attribute 'changelog_register_time'"
• BZ - 1123328 - Upgrade/Install of redhat-storage-server-3.0.0.3-1.el6rhs fails with dependency error on abrt >= 2.0.8-23
• BZ - 1124583 - [SNAPSHOT] Snap mount doesn't inheret mount options from parent brick
• BZ - 1124692 - If snapshot is attempted when geo-replication session is live, error must be signalled.
• BZ - 1125818 - geo-rep: changelog_register fails when geo-rep started after session creation.
• BZ - 1125958 - DHT + NFS :- if Directory is created when sub-volume was down then unable to access Directory and its data when sub-volume is up again
• BZ - 1126720 - SMB:Yum update of samba packages leads to dependency error as RHEL has higher version of samba
• BZ - 1127748 - DHT + Rebalance + rename :- file is missing after rebalance is completed
• BZ - 1128647 - volume info files are not updated with the op-version and client-op-version
• BZ - 1131971 - samba related package dependency conflicts cause failure of layered install of RHSS3.0 on fully updated RHEL6
• BZ - 1132058 - [SNAPSHOT]: If the snapshoted brick has xfs options set as part of its creation, they are not automount upon reboot
• BZ - 1134316 - [SNAPSHOT]: snapshot create fails with error in log "Failed to open directory <xyz>, due to many open files"

CVEs

(none)

References

• https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/3/html