ay, January 11, 2015 7:25 AM
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [Neutron][L3][Devstack] Bug during delete
> floating IPs?
>
> I think Kevin is right - the actual root cause lies in plugins for
> which disassocia
From: Salvatore Orlando [sorla...@nicira.com]
Sent: Sunday, January 11, 2015 7:25 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][L3][Devstack] Bug during delete floating
IPs?
I think Kevin is right - the actual root cause lies in
I think Kevin is right - the actual root cause lies in plugins for which
disassociate_floating_ips returns None rather than an (empty) iterable.
A quick check revealed that at least:
neutron.plugins.embrane.base_plugin.EmbranePlugin
neutron.plugions.cisco.service_plugins.cisco_router_plugin.CiscoR
That only seems to bury the root cause because router_ids shouldn't be none
in this case with the reference L3 plugin.
The ML2 plugin calls disassociate_floatingips with do_notify set to False
so it should always be at least an empty set coming back.
Which L3 plugin were you using? Perhaps the im
This trivial patch fixes the tracebacks:
$ cat disassociate_floating_ips.patch
--- neutron/db/l3_db.py.orig2015-01-10 22:20:30.101506298 -0800
+++ neutron/db/l3_db.py 2015-01-10 22:24:18.111479818 -0800
@@ -1257,4 +1257,4 @@
def notify_routers_updated(self, context, router_ids):