Listeners not handling retry notification keys
Bug #1395966 reported by
Joshua Harlow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| taskflow |
Fix Released
|
High
|
Joshua Harlow | ||
Bug Description
Currently the listeners are having key errors when retry notifications occur. This is an incorrect side-effect and should be addressed.
| Changed in taskflow: | |
| assignee: | nobody → Joshua Harlow (harlowja) |
| importance: | Undecided → High |
| status: | New → Triaged |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to taskflow (master) | #1 |
| Changed in taskflow: | |
| status: | In Progress → Fix Committed |
| Changed in taskflow: | |
| milestone: | none → 0.6.0 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit b8e975e885e4f5a
Author: Joshua Harlow <email address hidden>
Date: Mon Nov 24 19:44:52 2014 -0800
Update listeners to ensure they correctly handle all atoms
Instead of looking for keys that are task specific (as well
as using the deprecated 'task_notifier') we need to update the
listeners to be agnostic to atoms (retry or task) that are
sent to them so that key errors do not occur when extracting
any data sent along with the event notification.
Fixes bug 1395966
Change-Id: Ib61b34b83203f5