networking-bgpvpn

  1. Bug #1517480
  2. Comment #8

Comment 8 for bug 1517480

Revision history for this message
Thomas Morin (tmmorin-orange) wrote : Re: port-delete succeeds but gives a traceback in neutron logs

I've also thought about putting data in the context object, but like you, I'm not sure the approach is supposed to work in the future.

On abort:

By bagpipe would be notified if another external thing causes the PORT_DELETE abort, by subscribing to and receiving an ABORT_DELETE event.

See http://docs.openstack.org/developer/neutron/devref/callbacks.html

Looking at the source, this does not seem to be implemented though.

The simple solution, for now, is I believe so simply act on the BEFORE_DELETE event.