Bug 1031107

Summary: georeplication fails with uppercase letters in hostname
Product: [Community] GlusterFS Reporter: Lukas Bezdicka <social>
Component: geo-replicationAssignee: Aravinda VK <avishwan>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: medium    
Version: pre-releaseCC: avishwan, bugs, gluster-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-22 15:40:20 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:

Description Lukas Bezdicka 2013-11-15 15:56:31 UTC 
Description of problem:
gluster volume geo-replication Staging msh-R97.int.na.example.com:Replica-Staging start fails.

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

How reproducible:
always

Steps to Reproduce:
1. create host with uppercase letters in hostname, idealy something like host above.
2. create two volumes and start geo-replicationg localy first volume on second
3. fail because of malformed url which isn't logged unless you run config instead of start

Actual results:

gluster volume geo-replication Staging msh-R97.int.na.example.com:Replica-Staging start - fails

gluster volume geo-replication Staging msh-R97.int.na.example.com:Replica-Staging config -  failure: malformed path log error

Expected results:
URL should be case insensitive (example http://en.wikipedia.org/wiki/Domain_name#Technical_requirements_and_process ) so it should work fine.

Additional info:
Comment 1 John Smith 2013-11-15 16:30:16 UTC 
See rfc4343 for further details on DNS case insensitivity: http://tools.ietf.org/html/rfc4343
Comment 2 Kaleb KEITHLEY 2015-10-22 15:40:20 UTC 
pre-release version is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.