openstack
/
python-tripleoclient
Code Issues Proposed changes

[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
This commit is contained in:
Alex Schultz 2020-08-10 13:45:14 -06:00
parent 9c87b97ef1
commit 846911ef53
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
tripleoclient/workflows/deployment.py
View File

@ -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":