Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1351873 - keystone.pp sets unreasonable execution time for keystone_manage token_flush
keystone.pp sets unreasonable execution time for keystone_manage token_flush
Product: RDO
Classification: Community
Component: openstack-packstack (Show other bugs)
Unspecified Linux
unspecified Severity low
: ---
: trunk
Assigned To: Martin Magr
Shai Revivo
Depends On:
  Show dependency treegraph
Reported: 2016-07-01 02:06 EDT by Erkki-T. Peura
Modified: 2017-06-18 04:05 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-06-18 04:05:08 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Erkki-T. Peura 2016-07-01 02:06:30 EDT
Description of problem:

    if hiera('CONFIG_KEYSTONE_DB_PURGE_ENABLE',false) {
      class { '::keystone::cron::token_flush':
        minute      => '*/1',
        require     => Service['crond'],
        destination => '/dev/null',

ends as '*/1 0 * * * keystone-manage token_flush >>/dev/null 2>&1'
in keystone crontab which means that command is executed every minute during hour 0

How reproducible:
Every installation

Steps to Reproduce:
1. set CONFIG_KEYSTONE_DB_PURGE_ENABLE=True in packstack answerfile
2. install packstack
3. check user keystone crontab

Actual results:
Crontab has line */1 0 * * * keystone-manage token_flush >>/dev/null 2>&1

Expected results:
Crontab has line 1 0 * * * keystone-manage token_flush >>/dev/null 2>&1

Additional info:
- Might cause deadlocks in DB
- Openstack Liberty and CentOS7
Comment 1 Christopher Brown 2017-06-18 04:05:08 EDT

Is this still an issue with current version of packstack?

Please re-open if that is the case.


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