Description of problem:
I suspected that the token flush cron job is pegging out my disk so I looked for a log file and to my surprise we log to /dev/null.  The upstream puppet-keystone installation shows we should log to "/var/log/keystone/keystone-tokenflush.log"

[root@overcloud-controller-0 keystone]# crontab -u keystone -l
# HEADER: This file was autogenerated at 2016-12-06 15:01:50 +0000 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 0 * * * sleep `expr ${RANDOM} \% 3600`; keystone-manage token_flush >>/dev/null 2>&1
[root@overcloud-controller-0 keystone]# pwd
/var/log/keystone
[root@overcloud-controller-0 keystone]# ls -la
total 2332
drwxr-x---.  2 keystone keystone      26 Nov 30 21:02 .
drwxr-xr-x. 40 root     root        4096 Dec  6 15:23 ..
-rw-rw----.  1 root     keystone 2379437 Dec  7 16:47 keystone.log


We need to log when this job runs and if issues arise from it for accountability.


Version-Release number of selected component (if applicable):
Newton
Build 2016-11-30.9

How reproducible:
Always (configuration issue)

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
log to keystone-token.log

Additional info:


Other cron jobs appear to log to /dev/null as well:

Heat:
1 0 * * * sleep `expr ${RANDOM} \% 3600`; heat-manage purge_deleted -g days 30 >>/dev/null 2>&1

Nova:
1 */12 * * * nova-manage db archive_deleted_rows --max_rows 100 >>/dev/null 2>&1

Cinder:
1 0 * * * cinder-manage db purge 30 >>/dev/null 2>&1