Verified as follows - Tokens get flushed as expected. [root@rhos-compute-node-02 ~]# yum list installed | grep openstack-puppet openstack-puppet-modules.noarch 1:7.1.5-6.el7ost @rhelosp-8.0-puddle [root@rhos-compute-node-02 ~]# sudo crontab -u keystone -l # HEADER: This file was autogenerated at 2017-08-30 11:24:44 -0400 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: keystone-manage token_flush PATH=/bin:/usr/bin:/usr/sbin SHELL=/bin/sh */1 * * * * keystone-manage token_flush >>/dev/null 2>&1 Database changed MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 1235 | +----------+ 1 row in set (0.00 sec) MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 1236 | +----------+ 1 row in set (0.00 sec) .. ... .... MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 9570 | +----------+ 1 row in set (0.00 sec) MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 9412 | +----------+ 1 row in set (0.00 sec) .. ... MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 9119 | +----------+ 1 row in set (0.00 sec) .. ... ... MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 8344 | +----------+ 1 row in set (0.01 sec) . .. Database changed MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 8034 | +----------+ 1 row in set (0.00 sec) .. ... MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 7733 | +----------+ 1 row in set (0.00 sec) .. ... MariaDB [keystone]> select count(*) from token; +----------+ | count(*) | +----------+ | 7577 | +----------+ 1 row in set (0.00 sec)
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:2691