Bug 926921 - Expired tokens are not deleted from the database
Summary: Expired tokens are not deleted from the database
Keywords:
Status: CLOSED DUPLICATE of bug 908355
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: 2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: 3.0
Assignee: RHOS Maint
QA Contact: Ami Jeain
URL:
Whiteboard:
: 888556 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-24 06:40 UTC by Gary Kotton
Modified: 2019-09-09 13:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-10 18:49:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1032633 0 None None None Never

Description Gary Kotton 2013-03-24 06:40:10 UTC
Description of problem:
A token that has expired is not deleted from the database.

Version-Release number of selected component (if applicable):


How reproducible:
Run the Quantum l3 agent - this connects to the quantum service every 3 seconds - creating ~ 16k tokens a day

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Alan Pevec 2013-03-26 22:11:20 UTC
(In reply to comment #0)
> Run the Quantum l3 agent - this connects to the quantum service every 3
> seconds - creating ~ 16k tokens a day

Agent could cache the token and renew it only when it's about to expire.

Workaround from upstream bug is manual database cleanup:

sql> DELETE FROM token WHERE expired <= NOW();

Also proposed as a new keystone-manage sub-command:
https://blueprints.launchpad.net/keystone/+spec/keystone-manage-token-flush

Comment 3 Alan Pevec 2013-04-03 21:10:40 UTC
*** Bug 888556 has been marked as a duplicate of this bug. ***

Comment 4 Adam Young 2013-04-10 18:49:47 UTC

*** This bug has been marked as a duplicate of bug 908355 ***


Note You need to log in before you can comment on or make changes to this bug.