Activity log for bug #1022614
Date | Who | What changed | Old value | New value | Message |
---|---|---|---|---|---|
2012-07-09 16:01:37 | Maru Newby | bug | added bug | ||
2012-07-09 16:02:13 | Maru Newby | 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 unlimited when using this backend. Note that fake memcache client in test_backend_memcache honours the expiry provided to set(), so this bug is effectively masked in testing. | 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_memcache honours the expiry provided to set(), so this bug is effectively masked in testing. | |
2012-07-09 16:14:17 | Joseph Heck | keystone: status | New | Triaged | |
2012-07-09 16:14:21 | Joseph Heck | keystone: importance | Undecided | Medium | |
2012-07-09 16:32:00 | Joseph Heck | keystone: importance | Medium | High | |
2012-07-09 16:32:10 | Joseph Heck | keystone: assignee | Maru Newby (maru) | ||
2012-07-09 16:38:36 | OpenStack Infra | keystone: status | Triaged | In Progress | |
2012-09-04 21:09:07 | Joseph Heck | keystone: milestone | folsom-rc1 | ||
2012-09-11 11:44:06 | Thierry Carrez | keystone: importance | High | Wishlist | |
2012-09-11 11:45:02 | Thierry Carrez | summary | Memcache token backend does not expire tokens | Document Memcache server needed system time setting | |
2012-09-13 09:34:35 | Thierry Carrez | keystone: status | In Progress | Fix Committed | |
2012-09-14 14:37:23 | Thierry Carrez | keystone: status | Fix Committed | Fix Released | |
2012-09-27 15:05:38 | Thierry Carrez | keystone: milestone | folsom-rc1 | 2012.2 |