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: If98c83c16e981353780573f6f0f0f737f1374ba1 Closes-Bug: #1904962
This commit is contained in:
parent
75b42f7b16
commit
5dceb01860
@ -1,7 +1,15 @@
|
||||
#
|
||||
# Class to execute placement-manage db sync
|
||||
#
|
||||
class placement::db::sync {
|
||||
# ==Parameters
|
||||
#
|
||||
# [*db_sync_timeout*]
|
||||
# (Optional) Timeout for the execution of the db_sync
|
||||
# Defaults to 300
|
||||
#
|
||||
class placement::db::sync(
|
||||
$db_sync_timeout = 300,
|
||||
) {
|
||||
|
||||
include placement::deps
|
||||
|
||||
@ -12,6 +20,7 @@ class placement::db::sync {
|
||||
refreshonly => true,
|
||||
try_sleep => 5,
|
||||
tries => 10,
|
||||
timeout => $db_sync_timeout,
|
||||
logoutput => on_failure,
|
||||
subscribe => [
|
||||
Anchor['placement::install::end'],
|
||||
|
@ -0,0 +1,3 @@
|
||||
---
|
||||
features:
|
||||
- Adds db_sync_timeout parameter to db sync.
|
@ -11,6 +11,7 @@ describe 'placement::db::sync' do
|
||||
:refreshonly => 'true',
|
||||
:try_sleep => 5,
|
||||
:tries => 10,
|
||||
:timeout => 300,
|
||||
:user => 'placement',
|
||||
:logoutput => 'on_failure',
|
||||
:subscribe => ['Anchor[placement::install::end]',
|
||||
|
Loading…
Reference in New Issue
Block a user