Browse Source

Handle non-existant plan when getting deployment status

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
(cherry picked from commit 1e13e461cd)
(cherry picked from commit 00e776dea7)
tags/8.7.1
James Slagle 1 year ago
parent
commit
ce0b276f8d

+ 5
- 0
releasenotes/notes/handle-no-deployment-status-a70a4b950171afbe.yaml View File

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

+ 2
- 2
workbooks/deployment.yaml View File

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

Loading…
Cancel
Save