bagpipe driver exception on neutron notifications should not stop ML2 processing

Bug #1520642 reported by Thomas Morin
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Thomas Morin

Bug Description

Currently, if an exception is thrown during the processing of a Neutron registry callback, this exception can interrupt ML2 processing.

We need to catch and log exceptions in the driver and not let them propagate to ML2 code.

Tags: bagpipe
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-bgpvpn (master)

Fix proposed to branch: master

Changed in bgpvpn:
assignee: nobody → Thomas Morin (tmmorin-orange)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-bgpvpn (master)

Submitter: Jenkins
Branch: master

commit 75d465f1d0d1be0015d762f019effa1f76595378
Author: Thomas Morin <email address hidden>
Date: Fri Nov 27 17:38:39 2015 +0100

    bagpipe driver: catch exceptions on Neutron notifs

    Adds try/except&log during notification processing
    to avoid propagating exceptions and interrupt ML2

    Closes-Bug: 1520642
    Change-Id: I59bf056fe472efeecfaaabf55766c81d5f16fcf6

Changed in bgpvpn:
status: In Progress → Fix Committed
Changed in bgpvpn:
milestone: none → 3.0.0
status: Fix Committed → Fix Released
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.