openstack/tripleo-common
Code Issues Proposed changes

Handle non-existant plan when getting deployment status

Browse Source 
Instead of failing the workflow when requesting the deployment status of
a non-existant plan, return a useful message instead.

Change-Id: Ic0333c0726b16d284a7cc54bc68e16ea1c9ebc4d
Partial-Bug: #1792637
This commit is contained in:
James Slagle 2018-09-14 17:01:26 -04:00
parent c0f41cae9f
commit 1e13e461cd
2 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
releasenotes/notes/handle-no-deployment-status-a70a4b950171afbe.yaml Normal file
View File

@ -0,0 +1,5 @@
---
fixes:
- The tripleo.deployment.v1.get_deployment_status workflow will no longer
error when requesting the deployment status for a non-existant plan. A
message is sent in the output instead of failing the workflow.

4
workbooks/deployment.yaml
View File

@ -697,8 +697,8 @@ workflows:
deployment_status: <% yaml_parse(task().result.last()) %> deployment_status: <% yaml_parse(task().result.last()) %>
on-complete: send_message on-complete: send_message
publish-on-error: publish-on-error:
status: FAILED message: No deployment status found for plan <% $.plan %>
message: <% task().result %> deployment_status: ""
send_message: send_message:
workflow: tripleo.messaging.v1.send workflow: tripleo.messaging.v1.send