Author: Kevin Benton <ke...@benton.pub>
Date: Mon Sep 19 16:02:45 2016 -0700
Always cleanup stale devices on DHCP setup failure
If the DHCP port setup process fails in the DHCP agent device
manager, it will throw a conflict exception, which will bubble
all of the way up to the main DHCP agent. The issue is that, during
a 'restart' call, the config files are wiped out while maintaining
the VIF before calling setup. This means that, if setup fails, there
is no reference to the interface name anymore so a subsequent destroy
will not first unplug the VIF before destroying the namespace.
This leaves a bunch of orphaned tap ports behind in the OVS case
that don't have an accessible namespace.
This patch addresses the issue by cleaning up all ports inside of
a namespace on a 'setup' failure before reraising the exception.
This ensures that the namespace is clear if destroy is called in the
future without another successful setup.
** Changed in: neutron
Status: In Progress => Fix Released
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
OVS port momentary lapse of reason
Status in neutron:
A phenomenon where OVS ports appear, disappear and show up again has
been experienced lately (e.g. ). This seems to be associated to
traces like below, where two separate interfaces get associated to the
same ofport right about the same time:
2016-09-19T17:34:48.065Z|00247|bridge|INFO|bridge br-int: added interface
qvo9d9ab7b1-59 on port 89
2016-09-19T17:34:48.077Z|00248|bridge|INFO|bridge br-int: added interface
tapc9e6d02e-2c on port 89
We need to figure out what's causing it, and fix it for good.
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : email@example.com
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp