Description of problem: Spurious failure of ./tests/basic/mount-nfs-auth.t and ./tests/geo-rep/georep-basic-dr-rsync.t are blocking NetBSD regression runs. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/11934 (tests: Moving ./tests/basic/mount-nfs-auth.t and ./tests/geo-rep/georep-basic-dr-rsync.t to bad test) posted (#1) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/11934 (tests: Moving ./tests/basic/mount-nfs-auth.t and ./tests/geo-rep/georep-basic-dr-rsync.t to bad test) posted (#2) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/12005 (tests: add arbiter-statfs.t to bad tests) posted (#1) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/12005 (tests: add arbiter-statfs.t/tier.t to bad tests) posted (#2) for review on master by Atin Mukherjee (amukherj)
REVIEW: http://review.gluster.org/12005 (tests: add arbiter-statfs.t/tier.t to bad tests) posted (#3) for review on master by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/12005 committed in master by Vijay Bellur (vbellur) ------ commit 255b4ba477f5163b59efee1c9f62845eb86067a2 Author: Atin Mukherjee <amukherj> Date: Mon Aug 24 16:20:06 2015 +0530 tests: add arbiter-statfs.t/tier.t to bad tests Recent regression links for proof: http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/9611/consoleFull https://build.gluster.org/job/rackspace-netbsd7-regression-triggered/9616/consoleFull https://build.gluster.org/job/rackspace-regression-2GB-triggered/13613/consoleFull Filed https://bugzilla.redhat.com/show_bug.cgi?id=1256588 for tracking arbiter-statfs.t spurious failure and https://bugzilla.redhat.com/show_bug.cgi?id=1231268 is going to track tier.t's issue. https://bugzilla.redhat.com/show_bug.cgi?id=1231268 Change-Id: I61dc8f3d3366b2c784e3ce82bd88900f2651cbef BUG: 1254127 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/12005 Reviewed-by: Vijay Bellur <vbellur> Tested-by: Vijay Bellur <vbellur>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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