spawn_n swallows exceptions in l3_agent
Bug #1254984 reported by
Jian Wen
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Low
|
Akanksha Agrawal |
Bug Description
eventlet.spawn_n is the same as eventlet.spawn, but it’s not possible
to know how the function terminated (i.e. no return value or
exceptions).[1] As a result, if process_router raises an exception,
_rpc_loop and _sync_routers_task will not be noticed.
Changed in neutron: | |
assignee: | nobody → Jian Wen (wenjianhn) |
Changed in neutron: | |
status: | In Progress → New |
assignee: | Jian Wen (wenjianhn) → nobody |
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
importance: | Undecided → Low |
status: | New → Incomplete |
status: | Incomplete → Confirmed |
Changed in neutron: | |
assignee: | nobody → Akanksha (akanksha-aha) |
Changed in neutron: | |
status: | Confirmed → In Progress |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/58668
Review: https:/