Description of problem: ----------------------------------------------------------------------- master:https://build.gluster.org/job/rackspace-regression-2GB-triggered/18980/console /tests/basic/afr/arbiter.t (Wstat: 0 Tests: 54 Failed: 3) Failed tests: 26, 29, 52 [root@ravi4 glusterfs]# show-test.sh tests/basic/afr/arbiter.t 26 43 TEST setfattr -n user.name -v value1 $M0/file [root@ravi4 glusterfs]# show-test.sh tests/basic/afr/arbiter.t 29 48 TEST setfattr -n user.name -v value2 $M0/file [root@ravi4 glusterfs]# show-test.sh tests/basic/afr/arbiter.t 52 81 TEST getfattr -n user.name $M0/file ----------------------------------------------------------------------- 3.7: https://build.gluster.org/job/rackspace-regression-2GB-triggered/18981/console ./tests/basic/afr/arbiter.t (Wstat: 0 Tests: 50 Failed: 3) Failed tests: 22, 25, 48 35 TEST setfattr -n user.name -v value1 $M0/file [root@ravi4 glusterfs]# show-test.sh tests/basic/afr/arbiter.t 25 40 TEST setfattr -n user.name -v value2 $M0/file [root@ravi4 glusterfs]# show-test.sh tests/basic/afr/arbiter.t 48 73 TEST getfattr -n user.name $M0/file
REVIEW: http://review.gluster.org/13667 (afr: Add more checks to check bricks being up) posted (#1) for review on master by Ravishankar N (ravishankar)
Just for the record: http://www.gluster.org/pipermail/gluster-devel/2016-March/048679.html
COMMIT: http://review.gluster.org/13667 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit e04bc451912733ab12bac28e47b4dd892df667d9 Author: Ravishankar N <ravishankar> Date: Thu Mar 10 15:53:23 2016 +0530 afr: Add more checks to check bricks being up Change-Id: I27f1a1c2f28d129ef7fafc676a8d3d6b82bcf2e4 BUG: 1316462 Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: http://review.gluster.org/13667 Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Pranith Kumar Karampuri <pkarampu> NetBSD-regression: NetBSD Build System <jenkins.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user