yahoo-eng-team team mailing list archive

[Paul Ward <wpward@xxxxxxxxxx>]

Public bug reported:

In implementing a mechanism driver for ML2, I see that any exceptions
raised by the mechanism driver are swallowed and all that's bubbled up
to the user is the generic MechanismDriverError.  This happens in
MechanismManager_call_on_drivers() in
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/managers.py.

It would be nice if the MechanismDriverError at least contained the
exception details from the last exception encountered in the driver
chain.

** Affects: neutron
     Importance: Undecided
     Assignee: Paul Ward (wpward)
         Status: New

** Changed in: neutron
     Assignee: (unassigned) => Paul Ward (wpward)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1273730

Title:
  MechanismDriverError hides original exception

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  In implementing a mechanism driver for ML2, I see that any exceptions
  raised by the mechanism driver are swallowed and all that's bubbled up
  to the user is the generic MechanismDriverError.  This happens in
  MechanismManager_call_on_drivers() in
  https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/managers.py.

  It would be nice if the MechanismDriverError at least contained the
  exception details from the last exception encountered in the driver
  chain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1273730/+subscriptions