IPV6 for swift proxy cache memcached config is inconsistent with keystoneauth
Bug #1610064 reported by
David Moreau Simard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
Keystone with memcached token caching uses python-memcached which has this parsing:
https:/
While Swift has this parsing:
https:/
The following would be the keystone config:
[keystone_
memcached_
While this would be the swift cache config:
[filter:cache]
use = egg:swift#memcache
memcache_servers = [::1]:11211
This isn't really a bug, just wish the format (and the parameter name) was consistent, it'd be more straightforward.
summary: |
- Parsing of IPV6 for swift proxy cache memcached config is inconsistent - with keystoneauth + IPV6 for swift proxy cache memcached config is inconsistent with + keystoneauth |
To post a comment you must log in.
We could chance the re in swift to something like "^(inet6: )?\[(?P< address> .*)\](: (?P<port> [0-9]+) )?$" so the 'inet6:' part it optional.. then we would support both forms.