CinderCronDbPurgeMaxDelay is not applied
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Takashi Kajinami |
Bug Description
In the latest tripleo-
deployment/
~~~
CinderCronDbP
type: string
description: >
Cron to move deleted instances to another table - Max Delay
default: '3600'
~~~
The parameter should have 3600 by default, but it is not applied on controllers.
~~~
[heat-admin@
# HEADER: This file was autogenerated at 2020-01-18 10:53:55 +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:
1 0 * * * cinder-manage db purge 30 >>/var/
~~~
I actually observed this in stable/queens, but I see that wrong parameter passed in t-h-t even in current master.
description: | updated |
description: | updated |
Changed in tripleo: | |
importance: | Undecided → Medium |
milestone: | none → ussuri-2 |
tags: | added: queens-backport-potential train-backport-potential |
Fix proposed to branch: master /review. opendev. org/703725
Review: https:/