Bug 1169707

Summary:	`gluster peer probe hostname` fails when hostname contains '_'
Product:	[Community] GlusterFS	Reporter:	lily <junli.li>
Component:	glusterd	Assignee:	bugs <bugs>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.4.2	CC:	bugs, gluster-bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1169784 (view as bug list)		Environment:
Last Closed:	2015-10-07 13:49:43 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:
Bug Blocks:	1169784

Description lily 2014-12-02 09:28:03 UTC

Description of problem:
`gluster peer probe hostname` fails when hostname contains '_'

Version-Release number of selected component (if applicable):
3.4.2-1

How reproducible:
always

Steps to Reproduce:
1.set a host'name to "n_***", such as "n_node";
2.on another node, execute `gluster peer probe n_node`
3.

Actual results:
2. 
n_node is an invalid address
Usage: peer probe <HOSTNAME>


Expected results:
2.
peer probe: success


Additional info:

Comment 1 Kaleb KEITHLEY 2014-12-02 12:40:09 UTC

RFC1035 indicates that only 0-9A-Za-z and '-' are legal characters in a hostname, however it was agreed during review that we should relax our hostname checking

Comment 2 Niels de Vos 2015-05-17 21:59:53 UTC

GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5.

This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs".

If there is no response by the end of the month, this bug will get automatically closed.

Comment 3 Kaleb KEITHLEY 2015-10-07 13:49:43 UTC

GlusterFS 3.4.x has reached end-of-life.

If this bug still exists in a later release please reopen this and change the version or open a new bug.

Comment 4 Kaleb KEITHLEY 2015-10-07 13:50:53 UTC

GlusterFS 3.4.x has reached end-of-life.\                                                   \                                                                               If this bug still exists in a later release please reopen this and change the version or open a new bug.