tripleoclient incorrectly handles the status messages in the deploy workflow
Bug #1766216 reported by
Dougal Matthews
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
James Slagle |
Bug Description
tripleoclient is waiting for a SUCCESS message, but it doesn't take into account that a sub-workflow could send one. The workflow tripleo.
It should wait for the final message, as that is the terminal message from that workflow execution.
tags: | added: queens-backport-potential |
Changed in tripleo: | |
status: | Confirmed → In Progress |
Changed in tripleo: | |
assignee: | Dougal Matthews (d0ugal) → James Slagle (james-slagle) |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/557356 /git.openstack. org/cgit/ openstack/ python- tripleoclient/ commit/ ?id=624037db017 960e6cd6ac18024 544c230c078031
Committed: https:/
Submitter: Zuul
Branch: master
commit 624037db017960e 6cd6ac18024544c 230c078031
Author: Steven Hardy <email address hidden>
Date: Wed Mar 28 15:22:00 2018 +0100
Don't exit on a RUNNING message for deploy workflow
This workflow is being updated to return a RUNNING status when the
workflow starts, so we don't want to assert that SUCCESS is the only
valid outcome anymore.
Related blueprint config- download- workflows
Co-Authored-By: Dougal Matthews <email address hidden> 9ed7ef32b16bb28 50411f7fcc6
Closes-Bug: #1766216
Change-Id: I78b4fc7673a403