Bug 1031107 - georeplication fails with uppercase letters in hostname
Summary: georeplication fails with uppercase letters in hostname
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: pre-release
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-15 15:56 UTC by Lukas Bezdicka
Modified: 2015-10-22 15:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-22 15:40:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.