yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #78223
[Bug 1824504] Re: arp responder will be created for a vlan port when port ip changed
Reviewed: https://review.opendev.org/652043
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5301ecf41b18e83abdc3c828cd64ce0111f9fcd1
Submitter: Zuul
Branch: master
commit 5301ecf41b18e83abdc3c828cd64ce0111f9fcd1
Author: Yang Li <yang.li@xxxxxxxxxxxx>
Date: Fri Apr 12 19:14:29 2019 +0800
Don't add arp responder for non tunnel network port
When the vlan and vxlan both exist in env, and l2population
and arp_responder are enabled, if we update a port's ip address
from vlan network, there will be arp responder related flows
added into br-tun, this will cause too many arp reply for
one arp request, and vm connections will be unnormal.
Closes-Bug: #1824504
Change-Id: I1b6154b9433a9442d3e0118dedfa01c4a9b4740b
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1824504
Title:
arp responder will be created for a vlan port when port ip changed
Status in neutron:
Fix Released
Bug description:
When the env contains both vlan and vxlan networks, if we enable l2pop and arp_responder function, when we update a vlan port's ip(VM1), the arp responder for this port will be created in br-tun.
When other compute‘s vm(VM2) ping VM1, the first arp destination is ff:ff:ff:ff:ff:ff, so every compute node will get this arp request, and because of arp responder, they will all create a arp reply to the VM2, all these arp reply packets will confuse physical switch, this will cause some network connection problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1824504/+subscriptions
References