Mistral doesn't send TASK_FAILED event in case of MistralException
Bug #1803746 reported by
Oleg Ovcharuk
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Oleg Ovcharuk |
Bug Description
In task_handler, there are a lot of functions which handle MistralException. They set task's state to ERROR and force fail workflow.
In this cases, actual event chain is:
WORKFLOW_LAUNCHED -> TASK_LAUNCHED -> WORKFLOW_FAILED
But the expected result is:
WORKFLOW_LAUNCHED -> TASK_LAUNCHED -> TASK_FAILED -> WORKFLOW_FAILED
This behavior obstruct to perform some rollback mechanisms, and so on.
Changed in mistral: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in mistral: | |
milestone: | none → stein-2 |
assignee: | nobody → Oleg Ovcharuk (vgvoleg) |
Changed in mistral: | |
milestone: | stein-2 → stein-3 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/619192
Review: https:/