heat-dbsync: increase timeout to 15 minutes
Increasing the heat db-sync from 5 to 15 minutes.
During an undercloud upgrade, the database can be very big and the
dbsync needs at least 10 minutes to run. So we override the Puppet
default value of 5 minutes to have a timeout of 15 minutes for
production deployments.
Change-Id: I7720bd68a3d6044287ccdebf77086a86c51ddd8f
Closes-Bug: #1726959
(cherry picked from commit a413314862
)
This commit is contained in:
parent
02d25849aa
commit
b0e0ed7f07
|
@ -26,7 +26,11 @@ Exec<| title == 'glance-manage db_sync' |> { refreshonly => false }
|
|||
Exec<| title == 'nova-db-sync-api' |> { refreshonly => false }
|
||||
Exec<| title == 'nova-db-sync' |> { refreshonly => false }
|
||||
Exec<| title == 'nova-db-online-data-migrations' |> { refreshonly => false }
|
||||
Exec<| title == 'heat-dbsync' |> { refreshonly => false }
|
||||
Exec<| title == 'heat-dbsync' |> {
|
||||
refreshonly => false,
|
||||
# Heat database on the undercloud can be really big, db-sync take usually at least 10 min.
|
||||
timeout => 900,
|
||||
}
|
||||
Exec<| title == 'aodh-db-sync' |> { refreshonly => false }
|
||||
Exec<| title == 'ironic-dbsync' |> { refreshonly => false }
|
||||
Exec<| title == 'mistral-db-sync' |> { refreshonly => false }
|
||||
|
|
|
@ -0,0 +1,8 @@
|
|||
---
|
||||
features:
|
||||
- |
|
||||
Increasing the heat db-sync from 5 to 15 minutes.
|
||||
During an undercloud upgrade, the database can be very big and the
|
||||
dbsync needs at least 10 minutes to run. So we override the Puppet
|
||||
default value of 5 minutes to have a timeout of 15 minutes for
|
||||
production deployments.
|
Loading…
Reference in New Issue