openstack/deb-mistral
Code Issues Proposed changes
d953cc82e6
deb-mistral/mistral/engine
History
Kevin Pouget 29d9e52857 Fix with-items task termination when sub-workflows fail 
When a with-items workflow based task is executing the sub-workflows
with concurrency, the task will stay in the RUNNING state if at least
one sub-workflow fail.

This behavior do not occurs for with-items action based tasks.
The issue is caused by a different management of the "accepted" flag
for actions than sub-workflows. A with-items task wait for the
termination of the concurrent executions by searching the "accepted"
ones. An action is set as accepted when its state change to "SUCCESS"
or "ERROR", while a sub-workflow is set to "accepted" when its state
change to "SUCCESS" only.

As for actions, this patch set the sub-workflows as accepted when fail.

Change-Id: Ie94af2a6a037d1184d127a27ea86d0752c03b3b2
Closes-Bug: #1555025
2016-03-09 12:09:36 +01:00
..
__init__.py Renaming "engine1" to "engine" 2015-04-09 17:47:36 +06:00
action_handler.py Merge "Support workflow id in execution operations" 2016-02-10 08:44:59 +00:00
base.py Support workflow id in execution operations 2016-02-04 23:59:12 +13:00
default_engine.py Merge "Support workflow id in execution operations" 2016-02-10 08:44:59 +00:00
default_executor.py Change LOG.warn to LOG.warning 2016-01-18 09:16:31 +00:00
policies.py If task fails on timeout - there is no clear message of failure 2015-12-23 13:29:22 +00:00
rpc.py Support workflow id in execution operations 2016-02-04 23:59:12 +13:00
task_handler.py Merge "Support workflow id in execution operations" 2016-02-10 08:44:59 +00:00
utils.py Remove unused logging import 2016-01-15 12:42:47 +08:00
workflow_handler.py Fix with-items task termination when sub-workflows fail 2016-03-09 12:09:36 +01:00