Dougal Matthews ab946c4a0e Fail the plan_management workflows when sending a "FAILED" message ... When Mistral workflows execute a second workflow (a sub-workflow execution), the parent workflow can't easily determine if sub-workflow failed. This is because the failure is communicated via a Zaqar message only and when a workflow ends with a successful Zaqar message it appears have been successful. This problem surfaces because parent workflows should have an "on-error" attribute but it is never called, as the workflow doesn't error. This change marks the workflow as failed if the message has the status "FAILED". Now when a sub-workflow fails, the task that called it should have the on-error triggered. Previously it would always go to on-success. Change-Id: Ie0f1d4e57505e9346ae3f0b25d755f55d73a255a Related-Bug: #1651704		2017-01-13 09:22:40 +00:00
..
baremetal.yaml	Merge "When making sub-workflow calls, pass the queue_name"	2017-01-09 09:24:33 +00:00
deployment.yaml	When making sub-workflow calls, pass the queue_name	2016-12-21 10:01:48 +00:00
plan_management.yaml	Fail the plan_management workflows when sending a "FAILED" message	2017-01-13 09:22:40 +00:00
scale.yaml	Block the scale down workflow until the stack is COMPLETE or FAILED	2016-12-19 12:01:39 -05:00
stack.yaml	Add utility workflow to wait for stack COMPLETE or FAILED	2016-12-13 11:26:38 -05:00
validations.yaml	Fix the validation ssh keys workflow	2016-11-07 12:26:45 +01:00