Bug 1470227 - Token flush does not complete when expired tokens becomes large enough
Summary: Token flush does not complete when expired tokens becomes large enough
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-puppet-modules
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: zstream
: 7.0 (Kilo)
Assignee: Harry Rybacki
QA Contact: Prasanth Anbalagan
URL:
Whiteboard:
Depends On: 1404324 1470230 1473713
Blocks: 1451122 1467120 1469457 1470221 1470226
TreeView+ depends on / blocked
 
Reported: 2017-07-12 14:36 UTC by Harry Rybacki
Modified: 2022-06-06 11:26 UTC (History)
23 users (show)

Fixed In Version: openstack-puppet-modules-2015.1.8-56.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1404324
Environment:
Last Closed: 2017-09-12 17:15:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1649616 0 None None None 2017-07-12 14:35:59 UTC
Red Hat Issue Tracker OSP-923 0 None None None 2022-06-06 11:26:50 UTC
Red Hat Product Errata RHBA-2017:2697 0 normal SHIPPED_LIVE openstack-packstack and openstack-puppet-modules bug fix advisory 2017-09-12 21:14:41 UTC

Comment 3 Prasanth Anbalagan 2017-08-31 12:43:51 UTC
Verified as follows - Token database gets flushed as expected.

*************
VERSION
*************

[root@lynx13 ~]# yum list installed | grep openstack-puppet
openstack-puppet-modules.noarch      2015.1.8-56.el7ost      @rhelosp-7.0-puddle

*********
LOGS
*********

[root@lynx13 ~]# sudo crontab -u keystone -l
# HEADER: This file was autogenerated at 2017-08-31 04:04:03 +0300 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: token-flush
*/1 * * * * /usr/bin/keystone-manage token_flush >/dev/null 2>&1


MariaDB [keystone]> select count(*) from token;
+----------+
| count(*) |
+----------+
|     1813 |
+----------+
1 row in set (0.00 sec)

MariaDB [keystone]> select count(*) from token;
+----------+
| count(*) |
+----------+
|     1814 |
+----------+
1 row in set (0.00 sec)
Database changed
+----------+
| count(*) |
+----------+
|     8725 |
+----------+
1 row in set (0.00 sec)

MariaDB [keystone]> Bye
[root@lynx13 ~]# date
Thu Aug 31 07:26:56 IDT 2017
[root@lynx13 ~]# 

MariaDB [(none)]> use keystone; select count(*) from token;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
+----------+
| count(*) |
+----------+
|       42 |
+----------+
1 row in set (0.00 sec)

MariaDB [keystone]> Bye
[root@lynx13 ~]# date
Thu Aug 31 15:41:49 IDT 2017

Comment 5 errata-xmlrpc 2017-09-12 17:15:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2697


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