Description of problem: Test file tests/bugs/quota/bug-1049323.t fails in fedora. The test that fails is "EXPECT "0" get_aux" where we return 0 when an auxiliary mount is created. In get_aux function we grep for "/var/run/gluster/<volname> to check if volume is up and return 0; In fedora, auxiliary mount is created on /run/gluster/<volname> and it causes the test to fail. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Test is not passing in Fedora Expected results: Test should pass in Fedora Additional info: The fix is simple. In get_aux function, grep for substring, "/run/gluster/<volname>" and it will pass both on Fedora and CentOS as well
REVIEW: http://review.gluster.org/13228 (tests/quota : fix failing test on auxiliary mount point) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/13228 (tests/quota : fix failing test on auxiliary mount point) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)
COMMIT: http://review.gluster.org/13228 committed in master by Vijay Bellur (vbellur) ------ commit ae165bd6d7c3a0130984cbd927be318146c7bbdd Author: Manikandan Selvaganesh <mselvaga> Date: Tue Jan 12 16:38:27 2016 +0530 tests/quota : fix failing test on auxiliary mount point In test file tests/bugs/quota/bug-1049323.t, test "EXPECT "0" get_aux" fails in Fedora. In get_aux function we grep for "/var/run/gluster/<volname>" to check if auxiliary mount point is created and we return 0 on success else we return 1. In fedora, auxiliary mount point is created on "/run/gluster/<volname>". So it fails on Fedora. The patch fixes it by just grepping for "/run/gluster/<volname>". Change-Id: Icb59395df4a98109eaa8199cbdbdedcd1cbef27a BUG: 1297740 Signed-off-by: Manikandan Selvaganesh <mselvaga> Reviewed-on: http://review.gluster.org/13228 Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Raghavendra Talur <rtalur> Tested-by: 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