Add a timeout in tripleoclient when waiting for Zaqar messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Juan Antonio Osorio Robles |
Bug Description
In tripleoclient after a workflow is started we wait for messages on the Zaqar queue. This is fine unless there is a problem in Zaqar and we never receive the messages.
We need to add a timeout, that can be specified by the caller (as a different sensible default will be required for different workflows). This should be added here: https:/
If we do reach a timeout, we should check the status of the workflow in Mistral and report that to the user - in theory, if we hit the timeout it means that the workflow has hit and error and a message has never been sent. (However, it could also be possible that a workflow has finished successfully but doesn't send a message due to an erorr in the workflow.)
Changed in tripleo: | |
assignee: | Dougal Matthews (d0ugal) → Julie Pichon (jpichon) |
Changed in tripleo: | |
assignee: | Julie Pichon (jpichon) → Dougal Matthews (d0ugal) |
Changed in tripleo: | |
milestone: | newton-rc1 → newton-rc2 |
Changed in tripleo: | |
milestone: | newton-rc2 → ocata-1 |
tags: | added: newton-backport-potential |
Changed in tripleo: | |
milestone: | ocata-1 → newton-rc3 |
tags: | removed: newton-backport-potential |
Changed in tripleo: | |
assignee: | Dougal Matthews (d0ugal) → nobody |
Changed in tripleo: | |
milestone: | ocata-1 → ocata-2 |
Changed in tripleo: | |
assignee: | nobody → Dougal Matthews (d0ugal) |
Changed in tripleo: | |
assignee: | Dougal Matthews (d0ugal) → Juan Antonio Osorio Robles (juan-osorio-robles) |
When I saw this, it appeared that the workflow was successful but the notification failed. It probably depends on where in the workflow it failed, considering that some workflows use zaqar as a gate.