dfdff78315
* Workflow output sometimes is not calculated correctly due to the race condition between different transactions: the one that checks workflow completion (i.e. calls "check_and_complete") and the one that processes action execution completion (i.e. calls "on_action_complete"). Calculating output sometimes was based on stale data cached by the SQLAlchemy session. To fix this, we just need to expire all objects in the session so that they are refreshed automatically if we read their state in order to make required calculations. See the bug description for more details on how the problem was observed. * Added another test for direct workflow that formally checks calculation of workflow output. It doesn't pretend to test the aforementioned issue (it can be reproduced only with a big number of attempts, and/or under load). It's for the sake of the test module completeness. Change-Id: I4a7e7fd9a4bbb6e93df169b4b40bc2d83ccfce89 Closes-Bug: #1792090
Team and repository tags
Mistral
Workflow Service for OpenStack cloud. This project aims to provide a mechanism to define tasks and workflows without writing code, manage and execute them in the cloud environment.
Project Resources
Mistral Official Documentation
Project status, bugs, and blueprints are tracked on Launchpad
CloudFlow: visualization tool for workflow executions on https://github.com/nokia/CloudFlow
Additional resources are linked from the project Wiki page
Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0
Release notes for the project can be found at: https://docs.openstack.org/releasenotes/mistral/