Red Hat Bugzilla – Bug 1564519
Incorrect setting in Cinder's db purge cron job
Last modified: 2018-08-29 12:36:17 EDT
Description of problem: The default value for Cinder's db purge cron job is incorrect. The THT parameter is defaulting the db purge job's "age in days" to 0, when instead it should match the default value in puppet-cinder, which is 30. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Deploy overcloud with default CinderCronDbPurgeAge 2. 3. Actual results: Display cinder's cron job on controller: [root@overcloud-controller-0 logrotate.d]# crontab -u cinder -l # HEADER: This file was autogenerated at 2018-04-05 21:04:24 +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: cinder-manage db purge PATH=/bin:/usr/bin:/usr/sbin SHELL=/bin/sh 1 0 * * * cinder-manage db purge 0 >>/var/log/cinder/cinder-rowsflush.log 2>&1 The "0" after "db purge" is the age setting that is incorrect. Expected results: The age should default to 30. Additional info:
Retargeting for OSP-13 since 11 is EOL.
Upstream patch should arrive via next RDO import (for 13z1).
Verified on: openstack-tripleo-heat-templates-8.0.4-4.el7ost.noarch # docker exec -it openstack-cinder-volume-docker-0 /bin/bash ()[root@controller-0 /]# crontab -u cinder -l # HEADER: This file was autogenerated at 2018-08-01 13:27:31 +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: cinder-manage db purge PATH=/bin:/usr/bin:/usr/sbin SHELL=/bin/sh 1 0 * * * cinder-manage db purge 30 >>/var/log/cinder/cinder-rowsflush.log 2>&1 As expected -> cinder-manage db purge 30
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-2018:2574