Red Hat Bugzilla – Bug 1232036
radosgw-agent can't use IPv6 destination
Last modified: 2017-07-30 12:04:23 EDT
Description of problem: Cannot specify IPv6 destination in radosgw-agent. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. Specify IPv6 address as the radosgw-agent destination, e.g.: $ radosgw-agent --src-access-key ... --src-secret-key ... --dest-access-key ... --dest-secret-key ... http://[1235:56:0:70:5:ffff:4:1234] Actual results: Fails: 2015-06-15 15:57:29,965 873 [radosgw_agent][ERROR ] NetworkError: unable to connect to [1235:56:0:70:5:ffff:4:1234] [Errno 22] Invalid argument Expected results: Should not fails Additional info:
Document in release notes. Workaround: specifying a host name with and associated ipv6 address should work.
We will also need to drop Python 2.6 support because urlparse does not support IPV6 in 2.6
(In reply to Alfredo Deza from comment #4) > We will also need to drop Python 2.6 support because urlparse does not > support IPV6 in 2.6 From a 1.3 product perspective, this is fine. RHEL 7 ships Python 2.7.5, and Ubuntu Trusty ships Python 2.7.6. And those are the only platforms that 1.3.0 supports.
We are now issuing a warning only that this will not work in Python 2.6 and that hostnames should be a fine workaround. Pull request with changes at https://github.com/ceph/radosgw-agent/pull/31
merged commit 1afb6e0 into master
I think we should tag and release a new version upstream with these changes. Alfredo, Yehuda, should we go with "v1.3" ?
the currently released version is 1.2.2, this was a minor bugfix (no functionality was added), would you object to 1.2.3 ? I can get this built/pushed today.
(In reply to Alfredo Deza from comment #9) > the currently released version is 1.2.2, this was a minor bugfix (no > functionality was added), would you object to 1.2.3 ? No objection - that would be excellent.
1.2.3 has been released both to PyPI (https://pypi.python.org/pypi/radosgw-agent) and the ceph package repos.
Moving to 1.3.2.
We believe this to be fixed in the latest version of the RHCS 1.3 product; closing.