Bug 1426329

Summary:	[Ganesha] : Add comment to Ganesha HA config file ,about cluster name's length limitation
Product:	[Community] GlusterFS	Reporter:	Kaleb KEITHLEY <kkeithle>
Component:	common-ha	Assignee:	Kaleb KEITHLEY <kkeithle>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.10	CC:	asoman, bugs, rhs-bugs, sbhaloth, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.10.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1426326	Environment:
Last Closed:	2017-04-05 00:01:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1426326
Bug Blocks:

Comment 1 Worker Ant 2017-02-23 17:32:13 UTC

REVIEW: https://review.gluster.org/16736 (common-ha: cluster names must be 15 characters or less in length) posted (#1) for review on release-3.10 by Kaleb KEITHLEY (kkeithle)

Comment 2 Worker Ant 2017-02-24 12:23:55 UTC

COMMIT: https://review.gluster.org/16736 committed in release-3.10 by Kaleb KEITHLEY (kkeithle) 
------
commit e31a0b4f3255db8683e03c0a71665e98e03b4307
Author: Kaleb S. KEITHLEY <kkeithle>
Date:   Thu Feb 23 12:31:30 2017 -0500

    common-ha: cluster names must be 15 characters or less in length
    
    Change-Id: Ib9545865cc1fec922824de1be41673320248304b
    BUG: 1426329
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle>
    Reviewed-on: https://review.gluster.org/16736
    Smoke: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    Reviewed-by: soumya k <skoduri>

Comment 3 Shyamsundar 2017-04-05 00:01:13 UTC

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.10.1, please open a new bug report.

glusterfs-3.10.1 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/2017-April/030494.html
[2] https://www.gluster.org/pipermail/gluster-users/