allow delete_port to work when there are multiple floating ips
It is possible to associate multiple floating ip addresses with a single
port through the use of multiple *fixed* ip addresses, e.g.:
nova boot ... --nic net-id=my-net-id myserver
nova add-fixed-ip myserver my-net-id
nova add-floating-ip --fixed-address x.x.x.1 myserver y.y.y.y.1
nova add-floating-ip --fixed-address x.x.x.2 myserver y.y.y.y.2
In this situation, neutron.db.l3_db.disassociate_floatingips would throw
an exception:
Exception: Multiple floating IPs found for port <port-id>
This would prevent someone from deleting an instance that was associated
with multiple floating ips.
This patch corrects disassociate_floatingips so that it will
disassociate all floating ips associated with the port, allowing the
delete operation to proceed correctly.
Reviewed: https:/ /review. openstack. org/85432 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=bad87ce76ad 27f2a4b3c72e26e 2eccc2c9564b85
Committed: https:/
Submitter: Jenkins
Branch: master
commit bad87ce76ad27f2 a4b3c72e26e2ecc c2c9564b85
Author: Lars Kellogg-Stedman <email address hidden>
Date: Fri Apr 4 13:35:32 2014 -0400
allow delete_port to work when there are multiple floating ips
It is possible to associate multiple floating ip addresses with a single
port through the use of multiple *fixed* ip addresses, e.g.:
nova boot ... --nic net-id=my-net-id myserver
nova add-fixed-ip myserver my-net-id
nova add-floating-ip --fixed-address x.x.x.1 myserver y.y.y.y.1
nova add-floating-ip --fixed-address x.x.x.2 myserver y.y.y.y.2
In this situation, neutron. db.l3_db. disassociate_ floatingips would throw
an exception:
Exception: Multiple floating IPs found for port <port-id>
This would prevent someone from deleting an instance that was associated
with multiple floating ips.
This patch corrects disassociate_ floatingips so that it will
disassociate all floating ips associated with the port, allowing the
delete operation to proceed correctly.
Change-Id: I68a2131fa8ee80 828354c9db4ac40 5c3f77c3b90
Closes-bug: 1302701