DVR: Migrate centralized unbound floatingip to the respective host when the port is bound
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Swaminathan Vasudevan |
Bug Description
When unbound ports are associated with floatingIP in DVR, it implements the floatingIP in the dvr_snat node under the snat_namespace.
When the private ports are bound to a specific host, the floatingIPs are not moved or migrated to their respective hosts.
This can be reproduced by
1. Create a network
2. Create a subnet
3. Create a router and associate the subnet to the router
4. Assign a gateway to the router.
5. Then create a port on the given network with a specific IP.
6. Now create a FloatingIP on the external network.
7. Associate the FloatingIP to the created port.
8. At this point the port is not bound and so the floatingIP gets implemented in the Snat_namespace in the dvr_snat node.
9. Then within a few seconds, we create a VM with the given port-id instead of network-id.
10. Now when the VM is built then the port gets bound.
11. Now the floatingIP is not seen on the host where the VM resides.
Theoretically the FloatingIP should be migrated to the host where it is currently bound.
Changed in neutron: | |
status: | New → Confirmed |
assignee: | nobody → Swaminathan Vasudevan (swaminathan-vasudevan) |
Changed in neutron: | |
status: | Confirmed → In Progress |
tags: | added: neutron-proactive-backport-potential |
https:/ /review. openstack. org/#/c/ 505324/ In progress.