Document Memcache server needed system time setting
Bug #1022614 reported by
Maru Newby
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Wishlist
|
Maru Newby |
Bug Description
Using python-memcached, memcache get() calls do not appear to respect the expiry time submitted to set(). The memcache token backend appears to assume that keys will not be returned after the expiry passed to set, so token life is effectively unlimited when using this backend.
The fake memcache client in test_backend_
description: | updated |
Changed in keystone: | |
importance: | Medium → High |
assignee: | nobody → Maru Newby (maru) |
Changed in keystone: | |
milestone: | none → folsom-rc1 |
Changed in keystone: | |
status: | In Progress → Fix Committed |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
Maru - Is this a bug in keystone, a bug in python-memcache, or a bug in how we're using python-memcache?