Description of problem: Currently gluster source location is hard-coded in vagrant file. This path should be user configurable. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/14354 (extra/devel-vagrant: accept gluster src location from user) posted (#1) for review on master by Rajesh Joseph (rjoseph)
COMMIT: http://review.gluster.org/14354 committed in master by Jeff Darcy (jdarcy) ------ commit 57185759ccf4c43cf3143d917f782419625c743e Author: Rajesh Joseph <rjoseph> Date: Mon May 16 14:38:24 2016 +0530 extra/devel-vagrant: accept gluster src location from user Currently gluster source location is hard-coded in vagrantfile. Made the source location user configurable and also fixed minor issue with peer probe with single node. Change-Id: I7057a97d7372477ddbf01fbc8db949923dfd86e8 BUG: 1336354 Signed-off-by: Rajesh Joseph <rjoseph> Reviewed-on: http://review.gluster.org/14354 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Jeff Darcy <jdarcy>
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.9.0, please open a new bug report. glusterfs-3.9.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://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/