Public bug reported:
Switches outside the cloud try to access the old mac when reusing a floating IP
and fail.
This is only solved by initiating traffic from the VM, and updating the new MAC
at the external switch.
How to Reproduce:
1. Create and associate new Floating IP with VM and connect to external network
(ie - ping 8.8.8.8)
2. Delete the floating IP (Don't just disassociate it)
3. Create and Associate a new floating IP - it will likely be the same IP, only
with a different MAC address (new neutron port)
4. Ping this IP from an external network
Expected Result:
Ping should succeed
Actual Result:
IP is unreachable
Note: This will also happen when connecting a new neutron-router to the
network (INSTEAD of an old one) - new router will get the same IP of the
old one, but will have a different MAC.
Suggested Solution:
Neutron Ports should preform Gratuitous ARP upon
creation/connection/association/udpate - updating all immediate network
entities with the new owner of the old IP.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1268995
Title:
Reusing IPs (floating, routers) fails due to external MAC caching
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Switches outside the cloud try to access the old mac when reusing a floating
IP and fail.
This is only solved by initiating traffic from the VM, and updating the new
MAC at the external switch.
How to Reproduce:
1. Create and associate new Floating IP with VM and connect to external
network (ie - ping 8.8.8.8)
2. Delete the floating IP (Don't just disassociate it)
3. Create and Associate a new floating IP - it will likely be the same IP,
only with a different MAC address (new neutron port)
4. Ping this IP from an external network
Expected Result:
Ping should succeed
Actual Result:
IP is unreachable
Note: This will also happen when connecting a new neutron-router to
the network (INSTEAD of an old one) - new router will get the same IP
of the old one, but will have a different MAC.
Suggested Solution:
Neutron Ports should preform Gratuitous ARP upon
creation/connection/association/udpate - updating all immediate network
entities with the new owner of the old IP.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1268995/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
