Bug 1328180

Summary: No keystone token flushing job on the undercloud machine
Product: Red Hat OpenStack Reporter: Udi Kalifon <ukalifon>
Component: rhosp-directorAssignee: Angus Thomas <athomas>
Status: CLOSED DUPLICATE QA Contact: Arik Chernetsky <achernet>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 8.0 (Liberty)CC: dbecker, mburns, morazi, rhel-osp-director-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-18 15:56:49 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:

Description Udi Kalifon 2016-04-18 15:29:47 UTC
Description of problem:
My instack machine ran out of disk space, and became unusable as all the services went down one by one (including rabbit). I was able to free up 2.1GB just by calling keystone-manage token_flush, and that's just in 1 day (I guess the upgrade process generates a lot of tokens?).

On the overcloud there is a cron job that calls the token flushing routinely to prevent the infinite inflation. I could find no similar job on the undercloud. 

I also made a clean install of 8.0 and there is no cleaning job defined on the undercloud node, this is defined only on the controllers.


Version-Release number of selected component (if applicable):
python-tripleoclient-0.3.4-3.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Install the undercloud
2. Run 'sudo crontab -l -u keystone'


Actual results:
No cron job defined


Expected results:
Same as for the controllers on the overcloud. You should see this job defined:
1 0 * * * sleep `expr ${RANDOM} \% 3600`; keystone-manage token_flush >>/dev/null 2>&1

Comment 2 Mike Burns 2016-04-18 15:56:49 UTC

*** This bug has been marked as a duplicate of bug 1289614 ***