Allow db sync timeouts to be configurable

As Openstack projects continue to have longer database migration
chains, the Puppet default timeout of 300 seconds for an execution
is becoming too short a duration on some hardware, leading to timeouts.
As projects continue to add more migration scripts without pruning
the base, timeouts will continue to become more frequent unless
this time can be expanded.

Change-Id: Ia353f278db9426d29617d6c274fef0c8b71c53e1
Closes-Bug: #1904962
This commit is contained in:
ZhongShengping 2020-11-23 09:27:52 +08:00
parent c17a1d703e
commit 16eff399ad
3 changed files with 12 additions and 2 deletions

View File

@ -12,9 +12,14 @@
# (Optional) Run db_sync by this system group.
# Default to ec2api
#
# [*db_sync_timeout*]
# (Optional) Timeout for the execution of the db_sync
# Defaults to 300
#
class ec2api::db::sync (
$system_user = 'ec2api',
$system_group = 'ec2api',
$system_user = 'ec2api',
$system_group = 'ec2api',
$db_sync_timeout = 300,
) {
include ec2api::deps
@ -27,6 +32,7 @@ class ec2api::db::sync (
refreshonly => true,
try_sleep => 5,
tries => 10,
timeout => $db_sync_timeout,
logoutput => on_failure,
subscribe => [
Anchor['ec2api::install::end'],

View File

@ -0,0 +1,3 @@
---
features:
- Adds db_sync_timeout parameter to db sync.

View File

@ -15,6 +15,7 @@ describe 'ec2api::db::sync' do
:refreshonly => true,
:try_sleep => 5,
:tries => 10,
:timeout => 300,
:logoutput => 'on_failure',
:subscribe => [
'Anchor[ec2api::install::end]',