wait_for_introspection_to_finish_error set status FAILED

Currently when wait_for_introspection_to_finish_error is reached,
the _introspect workflow will pass as a success even when it
actually failed. This means that the retry logic in the calling
workflow is never triggered.

wait_for_introspection_to_finish_error is hit in downstream CI
when ironic-introspector is under too much load to respond
to status poll requests.

This change also ensures callers to the
tripleo.baremetal.v1.introspect can override the default concurrency
so that this can be changed when required.

Change-Id: Ifd88ff9175bc6ca583e3826c59787680e25fbea3
Partial-Bug: #1836976
This commit is contained in:
Steve Baker 2019-07-24 00:34:26 +00:00
parent 46a6432a6e
commit c31faaa286
1 changed files with 5 additions and 2 deletions

View File

@ -498,9 +498,10 @@ workflows:
on-success: send_message
wait_for_introspection_to_finish_error:
publish:
message: <% "Introspection of node {0} timed out.".format($.node_uuid) %>
on-success: send_message
publish:
status: FAILED
message: <% "Introspection of node {0} failed.".format($.node_uuid) %>
send_message:
workflow: tripleo.messaging.v1.send
@ -646,6 +647,7 @@ workflows:
input:
- run_validations: False
- queue_name: tripleo
- concurrency: 20
tags:
- tripleo-common-managed
@ -684,6 +686,7 @@ workflows:
node_uuids: <% $.managed_nodes %>
run_validations: <% $.run_validations %>
queue_name: <% $.queue_name %>
concurrency: <% $.concurrency %>
publish:
introspected_nodes: <% task().result.introspected_nodes %>