Keystone token_flush execution may fail because of full transaction log in DB2
Bug #1257323 reported by
John Warren
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
Medium
|
John Warren | ||
Bug Description
If there is a high number of expired tokens, a user may get the following error message:
$ keystone-manage token_flush
2013-11-18 02:11:09.491 3806 CRITICAL keystone [-] (InternalError) ibm_db_
| Changed in keystone: | |
| assignee: | nobody → John Warren (jswarren) |
| status: | New → In Progress |
| Changed in keystone: | |
| importance: | Undecided → Medium |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to keystone (master) | #1 |
| Changed in keystone: | |
| status: | In Progress → Fix Committed |
| Changed in keystone: | |
| milestone: | none → icehouse-2 |
| status: | Fix Committed → Fix Released |
| Changed in keystone: | |
| milestone: | icehouse-2 → 2014.1 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5dc675f193a1dba
Author: John Warren <email address hidden>
Date: Mon Dec 2 19:51:41 2013 +0000
Flush tokens in batches with DB2
When there is a very large number of expired tokens to be flushed,
keystone-manage token_flush will fail with DB2 because it fills
the transaction log. This fix causes tokens to be flushed with DB2 in
batches of 100 at a time to prevent the transaction log from
filling up.
Closes-Bug: #1257323
Change-Id: Ic57d8795a99546