WF execution stays in RUNNING although task and action executions are in SUCCESS
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Moshe Elisha |
Bug Description
Hi,
I have created a workflow and executed it.
The actions executions are all in SUCCESS.
The task executions are all in SUCCESS.
The workflow execution is still in RUNNING.
I see one ERROR line in the logs and it might be related - os-mistral-01 mistral-engine.log:
2015-11-19 19:52:23.654 2034 ERROR oslo_messaging.
2015-11-19 19:52:23.655 2034 DEBUG oslo_messaging.
2015-11-19 19:52:23.668 2034 INFO oslo_messaging.
2015-11-19 19:52:23.675 2034 DEBUG oslo_messaging.
2015-11-19 19:52:24.673 2034 INFO oslo_messaging.
2015-11-19 19:52:24.681 2034 DEBUG oslo_messaging.
In the attached ZIP you will find:
* The workflow used
* The cmd output showing the scenario
* The Mistral logs (from all three servers)
Changed in mistral: | |
importance: | Undecided → High |
status: | New → Triaged |
milestone: | none → mitaka-1 |
tags: | added: liberty-backport-potential |
Changed in mistral: | |
assignee: | nobody → Moshe Elisha (melisha) |
Changed in mistral: | |
milestone: | mitaka-1 → 2.0.0 |
I am able to reproduce this bug. In other occurrences of the same failed scenario I don't see the "ERROR oslo_messaging. _drivers. impl_qpid" - so that ERROR might not be related to the bug