try to check if there are floatingips on the VMs on that subnet 962b8364-a2b4-46cc-95be-28cbab62b8c2
On Tue, Aug 5, 2014 at 3:24 PM, Sayali Lunkad <[email protected]> wrote: > Hi, > > The issue was resolved by following the commands below. > > neutron port-update <port-id> --device_owner clear > neutron port-delete <port-id> > neutron router-delete <router-id> > > Thanks, > Sayali. > > > > > On Sat, Aug 2, 2014 at 3:49 PM, Sayali Lunkad <[email protected]> > wrote: > >> Hi Zzelle, >> >> Thanks for the prompt response. >> As you mentioned I cleared all the routes using >> >> *neutron router-update 2f16d846-b6aa-43a3-adbe-7f91a1389b7f --routes >> action=clear * >> So to see the router status I run this: >> >> >> >> >> >> >> >> >> >> >> >> >> >> * neutron router-show 2f16d846-b6aa-43a3-adbe-7f91a1389b7f >> +-----------------------+--------------------------------------+| >> Field | Value >> |+-----------------------+--------------------------------------+ | >> admin_state_up | True || >> external_gateway_info | || >> id | 2f16d846-b6aa-43a3-adbe-7f91a1389b7f || >> name | router0 | | >> routes | || >> status | ACTIVE || >> tenant_id | 315561c9a19e4794ac4f4364c842254f >> |+-----------------------+--------------------------------------+ * >> After that I try to unbind the subnet using the command below but the >> same problem persists. >> >> >> *neutron router-interface-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f >> 962b8364-a2b4-46cc-95be-28cbab62b8c2 >> 409-{u'NeutronError': {u'message': u'Router interface for subnet >> 962b8364-a2b4-46cc-95be-28cbab62b8c2 on router >> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f cannot be deleted, as it is required >> by one or more routes.', u'type': u'RouterInterfaceInUseByRoute', >> u'detail': u''}} >> >> I am confused at this point as all the routes have been cleared but still >> it is throwing an error saying the router is required by multiple routes. >> >> Thanks, >> Sayali. >> >> >> On Sat, Aug 2, 2014 at 3:25 PM, ZZelle <[email protected]> wrote: >> >>> First command is of course: >>> * neutron router-show **2f16d846-b6aa-43a3-adbe-* >>> *7f91a1389b7f * >>> not >>> * neutron router-update **2f16d846-b6aa-43a3-adbe-**7f91a1389b7f* >>> >>> >>> On Sat, Aug 2, 2014 at 11:54 AM, ZZelle <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> According to the first error message, the subnet you try to unbind is >>>> used in router routes, you can see current router routes using: >>>> >>>> *neutron router-update **2f16d846-b6aa-43a3-adbe-**7f91a1389b7f* >>>> >>>> you need to update them before unbind: >>>> >>>> * neutron router-update **2f16d846-b6aa-43a3-adbe-* >>>> *7f91a1389b7f --routes type=dict list=true destination=...,nexthop=... >>>> [destination=...,nexthop=...[...]] * >>>> or clear router routes: >>>> >>>> >>>> >>>> * neutron router-update 2f16d846-b6aa-43a3-adbe-7f91a1389b7f --routes >>>> action=clear * >>>> And finally retry to unbind the subnet. >>>> >>>> >>>> >>>> Cédric, >>>> ZZelle@IRC >>>> >>>> >>>> On Sat, Aug 2, 2014 at 9:56 AM, Sayali Lunkad <[email protected]> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> I am facing trouble deleting a router from my openstack deployment. >>>>> >>>>> I have tried the following commands on the *controller node* and >>>>> pasted the output. >>>>> >>>>> *neutron router-interface-delete* >>>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f 962b8364-a2b4-46cc-95be-28cbab62b8c2 >>>>> 409-{u'NeutronError': {u'message': u'Router interface for subnet >>>>> 962b8364-a2b4-46cc-95be-28cbab62b8c2 on router >>>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f cannot be deleted, as it is required >>>>> by one or more routes.', u'type': u'RouterInterfaceInUseByRoute', >>>>> u'detail': u''}} >>>>> >>>>> *neutron port-delete* ec1aac66-481d-488e-860b-53b88d950ac7 >>>>> 409-{u'NeutronError': {u'message': u'Port >>>>> ec1aac66-481d-488e-860b-53b88d950ac7 has owner network:router_interface >>>>> and >>>>> therefore cannot be deleted directly via the port API.', u'type': >>>>> u'L3PortInUse', u'detail': u''}} >>>>> >>>>> *neutron router-delete* 2f16d846-b6aa-43a3-adbe-7f91a1389b7f >>>>> 409-{u'NeutronError': {u'message': u'Router >>>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f still has active ports', u'type': >>>>> u'RouterInUse', u'detail': u''}} >>>>> >>>>> *neutron l3-agent-router-remove* 7a977e23-767f-418e-8429-651c4232548c >>>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f >>>>> This removes the router from the l3 agent and attaches it to another >>>>> one as seen below. >>>>> >>>>> *neutron l3-agent-list-hosting-router* >>>>> 2f16d846-b6aa-43a3-adbe-7f91a1389b7f >>>>> >>>>> +--------------------------------------+----------------------+----------------+-------+ >>>>> | id | host | >>>>> admin_state_up | alive | >>>>> >>>>> +--------------------------------------+----------------------+----------------+-------+ >>>>> | 96e1371a-be03-42ed-8141-3b0027d3a82f | alln01-1-csx-net-004 | >>>>> True | :-) | >>>>> >>>>> +--------------------------------------+----------------------+----------------+-------+ >>>>> >>>>> >>>>> I have also run the commands below on the *network node* which worked >>>>> fine. >>>>> >>>>> *ip netns delete* qrouter-2f16d846-b6aa-43a3-adbe-7f91a1389b7f >>>>> >>>>> *ovs-vsctl del-port* br-int qr-ec1aac66-48 >>>>> >>>>> Could someone please tell me what can be done to delete the router or >>>>> is this some bug I am hitting. >>>>> >>>>> Thanks, >>>>> Sayali. >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 > >
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
