I suspect the CI tests on jenkins.openstack.org succeeded because it is using keystoneclient 0.2.2 rather than the latest from git.
Commit 3dfb8437 in keystoneclient introduced a flag called _use_keystone_cache in keystoneclient/middleware/auth_token.py (in _cache_store):
# we need to special-case set() because of the incompatibility between
# Swift MemcacheRing and python-memcached. See
# https://bugs.launchpad.net/swift/+bug/1095730
if self._use_keystone_cache: self._cache.set(key, data_to_store, time=self.token_cache_time)
else: self._cache.set(key, data_to_store, timeout=self.token_cache_time)
That flag is set to false in the keystone tests even though they are using "FakeMemcache" which should use the time= kwarg rather than timeout.
Since LP 1095730 has been resolved I think the _use_keystone_cache flag can be removed altogether and this integration bug between keystone and keystoneclient will be resolved.
I suspect the CI tests on jenkins. openstack. org succeeded because it is using keystoneclient 0.2.2 rather than the latest from git.
Commit 3dfb8437 in keystoneclient introduced a flag called _use_keystone_cache in keystoneclient/ middleware/ auth_token. py (in _cache_store):
# we need to special-case set() because of the incompatibility between /bugs.launchpad .net/swift/ +bug/1095730 keystone_ cache:
self. _cache. set(key,
data_to_ store,
time=self. token_cache_ time)
self. _cache. set(key,
data_to_ store,
timeout= self.token_ cache_time)
# Swift MemcacheRing and python-memcached. See
# https:/
if self._use_
else:
That flag is set to false in the keystone tests even though they are using "FakeMemcache" which should use the time= kwarg rather than timeout.
Since LP 1095730 has been resolved I think the _use_keystone_cache flag can be removed altogether and this integration bug between keystone and keystoneclient will be resolved.