07a1a3f417
Since [0] _save_flow_detail and _save_atom_detail use tenacious.retry, it means that they no longer raise StorageException but a tenacious.RetryError which is not caught by the callers. Some jobs may have been incorrectly consumed (instead of being rescheduled) when StorageException was raised. Now tenacious reraises only the last exception (StorageException), which is correctly handled. [0] Ic6b0a78d20124cc027468ecc6aeff189c25d1a8a Closes-Bug: #2037050 Change-Id: I030dd8fc5b65833243cf0948af53dc1aeabf41d9
7 lines
180 B
YAML
7 lines
180 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixed an issue with the handling of exceptions when running a flow, some
|
|
jobs may have been incorrectly consumed (and not rescheduled) during
|
|
outages.
|