Description of problem: Spurious transport endpoint is not connected on tier regression tests Version-Release number of selected component (if applicable): How reproducible: spurious Steps to Reproduce: 1. run tier.t in loop Actual results: Eventually observe transport endpoint not connected In rare cases results in failed tests. Expected results: No such errors. Additional info: Problem due to unmounting gluster without exiting directory.
COMMIT: http://review.gluster.org/12327 committed in master by Dan Lambright (dlambrig) ------ commit bad9539437ca1d69e470159277bbb6b5675cbae3 Author: Dan Lambright <dlambrig> Date: Fri Oct 9 12:18:03 2015 -0400 cluster/tier: fix transpoint endpoint not connected in tier.t (rare) The script did not cleanly unmount/mount gluster and change the current working directory when stopping and starting the volume. Most of the time this problem would self-resolve before subsequent tests, but very occasionally races would lead to the errors/failures. Change-Id: I128b913a71e2745512ee81c3d71852311e3b4a1b BUG: 1270328 Signed-off-by: Dan Lambright <dlambrig> Reviewed-on: http://review.gluster.org/12327 Reviewed-by: Joseph Fernandes Tested-by: Gluster Build System <jenkins.com>
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