Added NFV-VIM timeouts to puppet configuration

The timeouts would be present for a freshly installed stx-10
version. But systems upgraded from older releases would not
have the timeout values present.

The absence of these timeouts can cause issues because default
timeouts do not always work out.

Depends-On: https://review.opendev.org/c/starlingx/nfv/+/958193

TEST PLAN
Pass: Run platform::nfv::runtime manifest on AIO-SX and
      verify config is updated

Closes-Bug: 2121376
Change-Id: I146c3e29dbeb0d93b59fb4a8e16ca0411f7425ac
Signed-off-by: sshathee <shunmugam.shatheesh@windriver.com>
This commit is contained in:
sshathee
2025-09-02 09:34:40 -04:00
parent df4183bcb1
commit 3cb945f63c

View File

@@ -43,6 +43,8 @@ class nfv::vim (
$deploy_start_timeout = 3600,
# sw_deploy_rollback uses timeout from sw_deploy_execute
$deploy_host_execute_timeout = 3600,
$deploy_host_retries = 3,
$deploy_host_retry_delay = 120,
$deploy_activate_timeout = 3600,
$deploy_activate_retries = 3,
$deploy_activate_retry_delay = 30,
@@ -109,6 +111,8 @@ class nfv::vim (
# SOFTWARE-DEPLOYMENT TIMEOUTS
'software-deploy/deploy_start_timeout': value => $deploy_start_timeout;
'software-deploy/deploy_host_execute_timeout': value => $deploy_host_execute_timeout;
'software-deploy/deploy_host_retries': value => $deploy_host_retries;
'software-deploy/deploy_host_retry_delay': value => $deploy_host_retry_delay;
'software-deploy/deploy_activate_timeout': value => $deploy_activate_timeout;
'software-deploy/deploy_activate_retries': value => $deploy_activate_retries;
'software-deploy/deploy_activate_retry_delay': value => $deploy_activate_retry_delay;