admin can not delete External Network because floatingip

[shake.chen]

HI

in admin role, I create External Network and router. and create tenant A and userA.

Now the userA login, create network and router, create VM1 and assign Floating IP , access well ,perfectly.

Now I try to in admin roles delete it.

1: delete userA , no problem
2: delete tenantA , no problem
3: delete vm1, no problem
4: delete router, no problem
5: delete External Networknet, report error, I try to delete the port in sub panel, also fail.
check the Neutrion server log

TRACE neutron.api.v2.resource L3PortInUse: Port 2e5fa663-22e0-4c9e-87cc-e89c12eff955 has owner network:floatingip and therefore cannot be deleted directly via the port API.

[ZhiQiang Fan (aji-zqfan)]

did neutron receive floatingip disassociate request?

[shake.chen (shake-chen)]

I think whern I delete vm, the neutron wourd receive floatingip disassociate request.

but now seem not. so I can not delete the External Network and the port.

[Salvatore Orlando (salvatore-orlando)]

Oleg, have you triaged this bug?
Is that perhaps related to the switch from OVS plugin to ML2?

[Oleg Bondarev (obondarev)]

Had no chance to reproduce yet, will try it with OVS shortly.

[Akihiro Motoki (amotoki)]

Deleting the external network fails because there is a floating IP on the external network.
It occurs with both OVS and ML2 plugins. I tested with the latest milestone-proposed (= RC2; commit a92b15e198b50f3acb9b6ed634543a0ba386af9c).

In my understanding, a floating IP is not released but disassociated when a VM is terminated,
and the floating IP should be deleted (released) manually.

Currently floating IP on an external network are not deleted automatically when deleting the external network.
I am not sure they should be deleted automatically or not.
Removing the external network is not a usual operation in a deployment (except a lab) and we should delete an external network carefully, so the current behavior sounds reasonable to me.

[Salvatore Orlando (salvatore-orlando)]

Akihiro,

thanks for the explanation.
It all makes sense, since a floating IP is actually a port on an external network.

I too don't see the urge for changing this behaviour; however on the other hand, it might be argued that a disassociated floating IP should be automatically garbage collected when its network is removed, in a way similar to AUTO_DELETE_PORT_OWNERS

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/53364

[yong sheng gong (gongysh)]

I think to delete *disassociated floatingips are reasonable when delete external networks.

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/53364
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=1763c80711993c55f4f13afe56f449b1dd6d3d3a
Submitter: Jenkins
Branch: master

commit 1763c80711993c55f4f13afe56f449b1dd6d3d3a
Author: Oleg Bondarev <email address hidden>
Date: Wed Oct 23 12:54:38 2013 +0400

    Delete disassociated floating ips on external network deletion

    Also remove redundant check for network in use in bigswitch plugin

    Closes-Bug: #1238439
    Closes-Bug: #1259144

    Change-Id: I7586f43c2e99be9df491c68bf1e8658994ffd263

[Haifeng.Yan (yanheven)]

I just tested this bug in icehous, the function is ok, you delete a tenant, but the floatingip is also belong to this tenant with it's

id,although this tenant is deleted.

[Yair Fried (yfried)]

The bug was fixed in Juno release. I don't think it needs backporting to Juno

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/icehouse
Review: https://review.openstack.org/135903

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/135903
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b9ade57c3dd182862d9fc487cc246e7e061e6000
Submitter: Jenkins
Branch: stable/icehouse

commit b9ade57c3dd182862d9fc487cc246e7e061e6000
Author: Oleg Bondarev <email address hidden>
Date: Wed Oct 23 12:54:38 2013 +0400

    Delete disassociated floating ips on external network deletion

    Also remove redundant check for network in use in bigswitch plugin

    Closes-Bug: #1238439
    Closes-Bug: #1259144
    (cherry picked from commit 1763c80711993c55f4f13afe56f449b1dd6d3d3a)

    Change-Id: I7586f43c2e99be9df491c68bf1e8658994ffd263