spawn_n swallows exceptions in l3_agent

Bug #1254984 reported by Jian Wen
10
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.

[1] http://eventlet.net/doc/basic_usage.html

Tags: l3-ipam-dhcp
Jian Wen (wenjianhn)
Changed in neutron:
assignee: nobody → Jian Wen (wenjianhn)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/58668

Changed in neutron:
status: New → In Progress
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)
goocher (farmerworking)
Changed in neutron:
status: Confirmed → In Progress
Revision history for this message
Assaf Muller (amuller) wrote :

The code has changed since the bug was filed and the problem has since went away, confirmed with Akanksha.

Changed in neutron:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.