REVIEW: http://review.gluster.org/10952 (common-ha: handle long node names and node names with '-' and '.' in them) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10952 (common-ha: handle long node names and node names with '-' and '.' in them) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10952 (common-ha: handle long node names and node names with '-' and '.' in them) posted (#3) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/10952 (common-ha: handle long node names and node names with '-' and '.' in them) posted (#4) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/11035 (common-ha: handle long node names and node names with '-' and '.' in them) posted (#1) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/11035 (common-ha: handle long node names and node names with '-' and '.' in them) posted (#2) for review on master by Kaleb KEITHLEY (kkeithle)
REVIEW: http://review.gluster.org/11035 (common-ha: handle long node names and node names with '-' and '.' in them) posted (#3) for review on master by Kaleb KEITHLEY (kkeithle)
COMMIT: http://review.gluster.org/11035 committed in master by Niels de Vos (ndevos) ------ commit 04791e4d53650eb108890e9ad9a809768a06987b Author: Kaleb S. KEITHLEY <kkeithle> Date: Mon Jun 1 14:02:58 2015 -0400 common-ha: handle long node names and node names with '-' and '.' in them sourcing the /etc/ganesha/ganesha-ha.conf file seemed like a simple and elegant solution for reading config params, but bash variable names do not allow '-' and '.' in them. Also fix incorrect path in shared volume mount Change-Id: I40140e5da0903221efd316de94dce40229263e15 BUG: 1225572 Signed-off-by: Kaleb S. KEITHLEY <kkeithle> Reviewed-on: http://review.gluster.org/11035 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Niels de Vos <ndevos>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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