Worker notify timeout condition not reset
Bug #1300373 reported by
Joshua Harlow
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| taskflow |
Fix Released
|
Undecided
|
Joshua Harlow | ||
Bug Description
It appears like if the worker is started/stopped repeatably that the notify timeout isn't reset, this will stop notifications from being sent out.
| Changed in taskflow: | |
| assignee: | nobody → Joshua Harlow (harlowja) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to taskflow (master) | #1 |
| Changed in taskflow: | |
| status: | New → Fix Committed |
| Changed in taskflow: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 0498a48e8fe913b
Author: Joshua Harlow <email address hidden>
Date: Sat Mar 29 17:14:25 2014 -0700
Worker executor adjustments
- Reset the notify_timeout on start (to ensure that the
notification thread will continue working on repeated
stops/starts)
- Adjust comment of stop/start method to reflect that more
than just the proxy thread is started and stopped.
Fixes bug 1300373
Change-Id: I534fa87d9f3b9c