Engine race condition between on_task_result and start_workflow/on_task_result
Bug #1395679 reported by
Renat Akhmerov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Critical
|
Renat Akhmerov |
Bug Description
If action completes fast enough then corresponding on_task_result() gets called before the first transaction in start_workflow() completes hence task DB instance may not exist yet.
The same can happen between two calls on_task_result().
Changed in mistral: | |
importance: | Undecided → Critical |
assignee: | nobody → Renat Akhmerov (rakhmerov) |
milestone: | none → kilo-1 |
Changed in mistral: | |
status: | New → In Progress |
Changed in mistral: | |
status: | In Progress → Fix Committed |
Changed in mistral: | |
status: | Fix Committed → Fix Released |
Changed in mistral: | |
milestone: | kilo-1 → 2015.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/137313
Review: https:/