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