yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #15166
[Bug 1115284] Re: StackTrace on 2012.1.4 middleware when storing token in memcache with SWIFT 1.7.4
** Changed in: keystone/essex
Status: New => Invalid
** Changed in: keystone/folsom
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1115284
Title:
StackTrace on 2012.1.4 middleware when storing token in memcache with
SWIFT 1.7.4
Status in OpenStack Identity (Keystone):
Invalid
Status in Keystone essex series:
Invalid
Status in Keystone folsom series:
Invalid
Bug description:
when integrating Keystone 2012.1.4 with SWIFT, and swift-proxy is configured to cache tokens in memcache, we get a response "500 internal server error" from swift because keystone.middleware.auth_token stacktraces with :
"TypeError: %d format: a number is required, not str" in two situations.
#1 when a new token wants to be cached
#2 when an invalid ( non existent or expired ) token is cached
For the #1 & #2 cases, we patched /usr/local/lib/python2.7/dist-
packages/keystone-2012.1.[VERS]-py2.7.egg/keystone/middleware/auth_token.py
in the line 151 and replaced :
self.token_cache_time = conf.get('token_cache_time', 300)
with
self.token_cache_time = int(conf.get('token_cache_time', 300))
We think its a big and anoying bug when you need this feature from keystone ( most of serious SWIFT implementations )
Thanks !!
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1115284/+subscriptions