Description of problem: cleanup test should unmount all stale mount points if any otherwise other test cases may fail. Version-Release number of selected component (if applicable): 3.6 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/8708 (test: cleanup should clean all left over (stale) mounts) posted (#2) for review on release-3.6 by Atin Mukherjee (amukherj)
COMMIT: http://review.gluster.org/8708 committed in release-3.6 by Vijay Bellur (vbellur) ------ commit 58e807c2c80c16af539b0472af43b666ec3c2d08 Author: Atin Mukherjee <amukherj> Date: Fri Sep 12 13:06:57 2014 +0530 test: cleanup should clean all left over (stale) mounts This is a temporary work around to fix the spurious failures seen in ec testcases. As per the initial analysis it looks like quota (glusterd_quota_initiate_fs_crawl) is causing a mount point in /tmp to be stale. Once the root cause is identified this fix can be reverted as well. Backport of http://review.gluster.org/#/c/8703/ Change-Id: I8686f144ed298124074f749e75c13028ec00be01 BUG: 1141187 Signed-off-by: Atin Mukherjee <amukherj> Reviewed-on: http://review.gluster.org/8703 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Justin Clift <justin> Reviewed-by: Xavier Hernandez <xhernandez> Reviewed-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/8708
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users