Set task failed when work service exceptionally suspended.
Bug #1922623 reported by
zack chen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| taskflow |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
When the worker node is suspended or closed due to an exception, the task running on the node will always be in the running state, resulting in the whole workflow suspened.
| Changed in taskflow: | |
| assignee: | nobody → zack chen (zackchen) |
Revision history for this message
| Michael Johnson (johnsom) wrote | #1 |
| Changed in taskflow: | |
| status: | New → Invalid |
| assignee: | zack chen (zackchen) → nobody |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on taskflow (master) | #2 |
To post a comment you must log in.
Can you give an example of this happening? Jobboard should already be doing this, so I'm trying to understand what is different in this condition.
Reproduction steps would be helpful.