Bug 1351873

Summary: keystone.pp sets unreasonable execution time for keystone_manage token_flush
Product: [Community] RDO Reporter: Erkki-T. Peura <erkki>
Component: openstack-packstackAssignee: Martin Magr <mmagr>
Status: CLOSED EOL QA Contact: Shai Revivo <srevivo>
Severity: low Docs Contact:
Priority: unspecified    
Version: trunkCC: aortega, chris.brown, derekh, srevivo
Target Milestone: ---   
Target Release: trunk   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-18 08:05:08 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 Erkki-T. Peura 2016-07-01 06:06:30 UTC 
Description of problem:
https://github.com/openstack/packstack/blob/master/packstack/puppet/modules/packstack/manifests/keystone.pp

    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 08:05:08 UTC 
Hello,

Is this still an issue with current version of packstack?

Please re-open if that is the case.

Thanks