memcache key length error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-keystoneclient (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Saucy |
Won't Fix
|
High
|
Yolanda Robla | ||
Trusty |
Fix Released
|
High
|
Unassigned |
Bug Description
Getting the following error with 1:0.3.2-
Note this was fixed upstream a while ago.
2013-11-13 09:37:49.827 14452 INFO glance.wsgi.server [-] Traceback (most recent call last):
File "/usr/lib/
result = self.applicatio
File "/usr/lib/
resp = self.call_func(req, *args, **self.kwargs)
File "/usr/lib/
return self.func(req, *args, **kwargs)
File "/usr/lib/
response = req.get_
File "/usr/lib/
application, catch_exc_
File "/usr/lib/
app_iter = application(
File "/usr/lib/
token_info = self._validate_
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
time=
File "/usr/lib/
return self._set("set", key, val, time, min_compress_len)
File "/usr/lib/
self.
File "/usr/lib/
% self.server_
MemcachedKeyLen
[Impact]
Invalid PKI tokens are cached in memcache using the entire token as
key. This triggers the familiar memcache key length error since a
PKI token is much longer than 250 characters.
[Test Case]
<< to be confirmed >>
1. Install keystone, configure it to use PKI authentication
2. When keystone interacts with other components, no exceptions should be triggered.
[Regression potential]
Minimal. Fix has been pushes upstream and tested, and only affects the PKI case of keystone.
description: | updated |
Changed in python-keystoneclient (Ubuntu Saucy): | |
assignee: | nobody → Yolanda Robla (yolanda.robla) |
description: | updated |
Reference upstream is bug 1206347 which is released in 0.4.x series; needs a backport for SRU.