From fa67cb17afde833b7a714dcf9bfd3376a7800c34 Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Wed, 22 Jan 2020 13:12:04 +0900 Subject: [PATCH] Fix incorrect parameter to set max delay in cinder db purge cron Closes-bug: #1860505 Change-Id: I5ed014fb1061379d7a7a8686d289c1303941dce9 (cherry picked from commit fa52709a871492b60f140e387044e24b1973594f) --- deployment/cinder/cinder-base.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deployment/cinder/cinder-base.yaml b/deployment/cinder/cinder-base.yaml index 57c4f953a6..d561f5cf80 100644 --- a/deployment/cinder/cinder-base.yaml +++ b/deployment/cinder/cinder-base.yaml @@ -134,7 +134,7 @@ outputs: cinder::cron::db_purge::user: {get_param: CinderCronDbPurgeUser} cinder::cron::db_purge::age: {get_param: CinderCronDbPurgeAge} cinder::cron::db_purge::destination: {get_param: CinderCronDbPurgeDestination} - cinder::cron::db_purge::max_delay: {get_param: CinderCronDbPurgeMaxDelay} + cinder::cron::db_purge::maxdelay: {get_param: CinderCronDbPurgeMaxDelay} cinder::glance::glance_api_servers: {get_param: [EndpointMap, GlanceInternal, uri]} cinder::keystone::service_user::send_service_user_token: true cinder::keystone::service_user::project_name: service