From 2491e49c3b9f37a8756c311f513d31963d3150f6 Mon Sep 17 00:00:00 2001 From: Dougal Matthews Date: Mon, 20 Nov 2017 11:30:14 +0000 Subject: [PATCH] Correct the failed status in the baremetal workflow Two tasks in the introspect workflow have incorrectly been sending "ERROR" statuses when they should have sent "FAILED". This then meant the workflow appeared to finish without errors (or failures). This is primarily a problem for the introspect_manageable_nodes workflow which then can't detect errors and reports that everything was successful. Change-Id: I34a91dd14bb19775ad62271def6ecb66398c84db Closes-Bug: #1733303 (cherry picked from commit 7a18b486a18cf179a29be113ed90d5129c59c00e) --- workbooks/baremetal.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/workbooks/baremetal.yaml b/workbooks/baremetal.yaml index 3db47922e..993df3322 100644 --- a/workbooks/baremetal.yaml +++ b/workbooks/baremetal.yaml @@ -591,7 +591,7 @@ workflows: max_retry_attempts_reached: publish: - status: ERROR + status: FAILED message: <% 'Retry limit reached with {0} nodes still failing introspection'.format($.failed_introspection.len()) %> on-complete: send_message @@ -603,7 +603,7 @@ workflows: unhandled_error: publish: - status: ERROR + status: FAILED message: "Unhandled workflow error" on-complete: send_message