+++ This bug was initially created as a clone of Bug #1358195 +++ Description of problem: On a faster machine the ps check is returning two pids including the glusterfsd process's right after that process forks. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Vijay Bellur on 2016-07-20 05:38:00 EDT --- REVIEW: http://review.gluster.org/14963 (tests: Fix spurious failure of tests/bugs/glusterd/bug-1111041.t) posted (#1) for review on master by Avra Sengupta (asengupt) --- Additional comment from Vijay Bellur on 2016-07-20 06:02:47 EDT --- REVIEW: http://review.gluster.org/14963 (tests: Fix spurious failure of tests/bugs/glusterd/bug-1111041.t) posted (#2) for review on master by Avra Sengupta (asengupt) --- Additional comment from Vijay Bellur on 2016-07-20 11:21:53 EDT --- COMMIT: http://review.gluster.org/14963 committed in master by Jeff Darcy (jdarcy) ------ commit be69510e670cb5ee893399ca1d7e7d2a60a9483c Author: Avra Sengupta <asengupt> Date: Wed Jul 20 15:04:01 2016 +0530 tests: Fix spurious failure of tests/bugs/glusterd/bug-1111041.t On a faster machine the ps check was returning two pids, including the glusterfsd process's pid, right after that, process forked. Hence removing that ps, as for the scope of this test, verifying the snapd pid from the status command itself is enough. Change-Id: I8bd8fc4ea406d96e3a47f952cfe44560b615dbe6 BUG: 1358195 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/14963 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Rajesh Joseph <rjoseph> Reviewed-by: Atin Mukherjee <amukherj> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org>
REVIEW: http://review.gluster.org/14969 (tests: Fix spurious failure of tests/bugs/glusterd/bug-1111041.t) posted (#1) for review on release-3.8 by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/14969 committed in release-3.8 by Atin Mukherjee (amukherj) ------ commit e19edd95b51a97ff2ad43736325fc8dbd54f53f6 Author: Avra Sengupta <asengupt> Date: Wed Jul 20 15:04:01 2016 +0530 tests: Fix spurious failure of tests/bugs/glusterd/bug-1111041.t On a faster machine the ps check was returning two pids, including the glusterfsd process's pid, right after that, process forked. Hence removing that ps, as for the scope of this test, verifying the snapd pid from the status command itself is enough. > Reviewed-on: http://review.gluster.org/14963 > Smoke: Gluster Build System <jenkins.org> > Reviewed-by: Rajesh Joseph <rjoseph> > Reviewed-by: Atin Mukherjee <amukherj> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> (cherry picked from commit be69510e670cb5ee893399ca1d7e7d2a60a9483c) Change-Id: I8bd8fc4ea406d96e3a47f952cfe44560b615dbe6 BUG: 1358591 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/14969 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj>
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.2, please open a new bug report. glusterfs-3.8.2 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://www.gluster.org/pipermail/announce/2016-August/000058.html [2] https://www.gluster.org/pipermail/gluster-users/