Engine raises the error 'Delayed call not found'
Bug #1428635 reported by
Nikolay Makhotkin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
High
|
Nikolay Makhotkin |
Bug Description
Steps to reproduce:
1. Run mistral
2. Run at least 2 engines
3. Run workflow where scheduler will be used (e.g. with policies: wait-before, wait-after or retry)
4. One of engines raises the error 'Delayed call not found'
The reason is that each engine instance also creates the scheduler process. The scheduler check DB on delayed calls every second therefore both schedulers tries to process this delayed call. Once the call was deleted from the DB, another scheduler also tries to delete it but it doesn't find the delayed call because it was already deleted.
The possible solution is to wrap delayed call processing into one transaction.
Changed in mistral: | |
status: | Fix Committed → Fix Released |
Changed in mistral: | |
milestone: | kilo-3 → 2015.1 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/161716
Review: https:/