[DNM] Tuning stack_retries of k8s FT in Zuul
Due to the performance of the zuul environment, it may take a long time to remove the kubernetes resource and an error may occur. This patch avoids errors by tuning the `kubernetes_vim.stack_retries` value in Tacker config. Change-Id: I0fc8d6748cf92f6384b6cdc49322f0f85f16afcd
This commit is contained in:
parent
278bb0abf5
commit
9e0d7834c2
|
@ -388,7 +388,11 @@
|
||||||
tls-proxy: false
|
tls-proxy: false
|
||||||
tox_install_siblings: false
|
tox_install_siblings: false
|
||||||
controller-tacker:
|
controller-tacker:
|
||||||
devstack_local_conf: {}
|
devstack_local_conf:
|
||||||
|
post-config:
|
||||||
|
$TACKER_CONF:
|
||||||
|
kubernetes_vim:
|
||||||
|
stack_retries: 110
|
||||||
devstack_services:
|
devstack_services:
|
||||||
ovn-controller: true
|
ovn-controller: true
|
||||||
ovn-northd: true
|
ovn-northd: true
|
||||||
|
|
Loading…
Reference in New Issue