Hi Aaron! The BUG report https://bugs.launchpad.net/neutron/+bug/1322945 is about this problem, I posted there the instructions to reproduce it...
Basically, after attaching a private IPv6 subnet to your L3 Router, it will break the "External Network" and its "Floating IPs", then, it becomes impossible to delete that "External Network"... It enters in a "stuck" state... Regards, Thiago On 27 May 2014 18:34, Aaron Rosen <[email protected]> wrote: > Hi, > > can you open a bug report on this and provide your setup configuration? I > just tested this with ML2 and wasn't able to reproduce the issue. > > arosen@arosen-MacBookPro:~/devstack$ neutron net-create asdf > --provider:network_type vlan --provider:segmentation_id 124 > --provider:physical_network asdf > Unable to create the network. The VLAN 124 on physical network asdf is in > use. > > arosen@arosen-MacBookPro:~/devstack$ neutron net-delete asdf > Deleted network: asdf > > Thanks, > > Aaron > > > On Fri, May 23, 2014 at 10:52 AM, Martinx - ジェームズ < > [email protected]> wrote: > >> Guys, >> >> I'm trying to delete a network in Neutron but it is failing, from Horizon >> it triggers the error message above (subject), and from CLI, it shows this: >> >> --- >> root@psuaa-1:~# neutron net-delete a1654832-8aac-42d5-8837-6d27b7421892 >> Request Failed: internal server error while processing your request. >> --- >> >> The logs shows: >> >> --- >> ==> /var/log/neutron/server.log <== >> 2014-05-21 11:49:54.242 5797 INFO neutron.wsgi [-] (5797) accepted >> ('2804:290:4:dead::10', 56908, 0, 0) >> >> 2014-05-21 11:49:54.245 5797 INFO urllib3.connectionpool [-] Starting new >> HTTP connection (1): psuaa-1.mng.tcmc.com.br >> 2014-05-21 11:49:54.332 5797 INFO neutron.wsgi >> [req-e1c4d6c4-71de-4bfa-a7db-f09fa0571377 None] 2804:290:4:dead::10 - - >> [21/May/2014 11:49:54] "GET >> /v2.0/networks.json?fields=id&id=a1654832-8aac-42d5-8837-6d27b7421892 >> HTTP/1.1" 200 251 0.089015 >> >> 2014-05-21 11:49:54.334 5797 INFO neutron.wsgi >> [req-e1c4d6c4-71de-4bfa-a7db-f09fa0571377 None] (5797) accepted >> ('2804:290:4:dead::10', 56910, 0, 0) >> >> 2014-05-21 11:49:54.380 5797 ERROR neutron.api.v2.resource >> [req-f216416d-8433-444f-9108-f4a17f5bf49d None] delete failed >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource Traceback >> (most recent call last): >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource File >> "/usr/lib/python2.7/dist-packages/neutron/api/v2/resource.py", line 87, in >> resource >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource result = >> method(request=request, **args) >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource File >> "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 449, in >> delete >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource >> obj_deleter(request.context, id, **kwargs) >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource File >> "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/plugin.py", line 494, >> in delete_network >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource >> self.type_manager.release_segment(session, segment) >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource File >> "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py", line >> 101, in release_segment >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource >> driver.obj.release_segment(session, segment) >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource >> AttributeError: 'NoneType' object has no attribute 'obj' >> 2014-05-21 11:49:54.380 5797 TRACE neutron.api.v2.resource >> 2014-05-21 11:49:54.383 5797 INFO neutron.wsgi >> [req-f216416d-8433-444f-9108-f4a17f5bf49d None] 2804:290:4:dead::10 - - >> [21/May/2014 11:49:54] "DELETE >> /v2.0/networks/a1654832-8aac-42d5-8837-6d27b7421892.json HTTP/1.1" 500 296 >> 0.048123 >> --- >> >> What can I do to delete a "net" that "doesn't want" to be deleted? Do I >> just need to clean some tables directly on mysql, for example... ? >> >> NOTE: I'm double posting it here on dev list, because on user list no one >> seems to be able to help me... Sorry BTW... :) >> >> Tks! >> Thiago >> >> _______________________________________________ >> OpenStack-dev mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
