Bug 1031107 - georeplication fails with uppercase letters in hostname
georeplication fails with uppercase letters in hostname
Status: CLOSED EOL
Product: GlusterFS
Classification: Community
Component: geo-replication (Show other bugs)
pre-release
Unspecified Unspecified
medium Severity unspecified
: ---
: ---
Assigned To: Aravinda VK
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-15 10:56 EST by Lukas Bezdicka
Modified: 2015-10-22 11:40 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-22 11:40:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Lukas Bezdicka 2013-11-15 10:56:31 EST
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 11:30:16 EST
See rfc4343 for further details on DNS case insensitivity: http://tools.ietf.org/html/rfc4343
Comment 2 Kaleb KEITHLEY 2015-10-22 11:40:20 EDT
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.