Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 926921

Summary: Expired tokens are not deleted from the database
Product: Red Hat OpenStack Reporter: Gary Kotton <gkotton>
Component: openstack-keystoneAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact: Ami Jeain <ajeain>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.1CC: apevec, ayoung, yeylon, ykaul
Target Milestone: betaKeywords: FutureFeature, Triaged
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-10 18:49:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***