From 846911ef53528e1f3437a179296bccb57d640387 Mon Sep 17 00:00:00 2001 From: Alex Schultz Date: Mon, 10 Aug 2020 13:45:14 -0600 Subject: [PATCH] [TRAIN-Only] Increase deploy workflow wait During the execution of the deploy plan, we will also run container image prepare in a dry run. This may still reach out to determine tags which can contribute to the process taking longer than 10 minutes in CI. We are doubling the wait time from 10 minutes to 20 minutes for now. Eventually we should probably not exit if the task is still running. We dropped this code in Ussuri so it only applies in Train. Change-Id: Ifa94bffcf4fadc5d4a87675b5d4a3357e8808ac3 Parial-Bug: #1891071 --- tripleoclient/workflows/deployment.py | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/tripleoclient/workflows/deployment.py b/tripleoclient/workflows/deployment.py index 550b16ab3..e6948b772 100644 --- a/tripleoclient/workflows/deployment.py +++ b/tripleoclient/workflows/deployment.py @@ -52,10 +52,11 @@ def deploy(log, clients, **workflow_input): ) # The deploy workflow ends once the Heat create/update starts. This - # means that is shouldn't take very long. Wait for 10 minutes for - # messages from the workflow. + # means that is shouldn't take very long. Wait 20 minutes for + # complection because this also includes some container image prepare + # generation which may reach out to an external resource. for payload in base.wait_for_messages(workflow_client, ws, execution, - 600): + 1200): status = payload.get('status', 'RUNNING') message = payload.get('message') if message and status == "RUNNING":