Bug 1287960

Summary:	Geo-Replication failes on uppercase hostnames
Product:	[Community] GlusterFS	Reporter:	Saravanakumar <sarumuga>
Component:	geo-replication	Assignee:	Saravanakumar <sarumuga>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.7.6	CC:	avishwan, bugs, cblum, chrisw, csaba, hgowtham, khiremat, nlevinki, sarumuga, storage-qa-internal
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.7.7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1265522	Environment:
Last Closed:	2016-02-14 13:15:49 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:	1264800, 1265522
Bug Blocks:

Comment 1 Vijay Bellur 2015-12-03 06:58:05 UTC

REVIEW: http://review.gluster.org/12862 (geo-rep: geo-rep to handle CAPS based Hostname) posted (#1) for review on release-3.7 by Saravanakumar Arumugam (sarumuga)

Comment 2 Vijay Bellur 2015-12-03 10:24:34 UTC

COMMIT: http://review.gluster.org/12862 committed in release-3.7 by Venky Shankar (vshankar) 
------
commit e0d9e617e3bddeb0f8746cf5bcab75b05b7eb679
Author: Saravanakumar Arumugam <sarumuga>
Date:   Wed Sep 23 12:21:40 2015 +0530

    geo-rep: geo-rep to handle CAPS based Hostname
    
    Problem:
    geo-replication session creation fails when Hostname
    is having CAPS in it.
    Issue is with the regex pattern which handles only small lettered
    Hostname.
    
    Fix:
    Fix the regex pattern to handle CAPS based hostname as well.
    
    Change-Id: I5c99c102e9706acc2b1fab1e6bf158e68beed373
    BUG: 1287960
    Signed-off-by: Saravanakumar Arumugam <sarumuga>
    Reviewed-on: http://review.gluster.org/12216
    Tested-by: NetBSD Build System <jenkins.org>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Milind Changire <mchangir>
    Reviewed-by: Aravinda VK <avishwan>
    Reviewed-by: Vijay Bellur <vbellur>
    (cherry picked from commit f6142e97c6219d2c1c482a414690020ed1275bdb)
    Reviewed-on: http://review.gluster.org/12862
    Reviewed-by: Venky Shankar <vshankar>

Comment 3 Kaushal 2016-04-19 07:49:44 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.7.7, please open a new bug report.

glusterfs-3.7.7 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] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user