yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1916761@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package neutron -
2:17.1.0+git2021012815.0fb63f7297-0ubuntu4

---------------
neutron (2:17.1.0+git2021012815.0fb63f7297-0ubuntu4) hirsute; urgency=medium

  * d/p/revert-dvr-remove-control-plane-arp-updates.patch: Cherry-picked
    from https://review.opendev.org/c/openstack/neutron/+/777903 to prevent
    permanent arp entries that never get deleted (LP: #1916761).

 -- Corey Bryant <corey.bryant@xxxxxxxxxxxxx>  Mon, 08 Mar 2021 10:49:14
-0500

** Changed in: neutron (Ubuntu Hirsute)
       Status: Triaged => 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/1916761

Title:
  [dvr] bound port permanent arp entries never deleted

Status in Ubuntu Cloud Archive:
  Triaged
Status in Ubuntu Cloud Archive train series:
  Triaged
Status in Ubuntu Cloud Archive ussuri series:
  Triaged
Status in Ubuntu Cloud Archive victoria series:
  Triaged
Status in neutron:
  In Progress
Status in neutron package in Ubuntu:
  Fix Released
Status in neutron source package in Focal:
  Triaged
Status in neutron source package in Groovy:
  Triaged
Status in neutron source package in Hirsute:
  Fix Released

Bug description:
  [Impact] [Test Case]
  With Openstack Ussuri using dvr-snat I do the following:

    * create port P1 with address A1 and create vm on node C1 with this port
    * associate floating ip with P1 and ping it
    * observe REACHABLE arp entry for A1 in qrouter arp cache
    * so far so good
    * restart the neutron-l3-agent
    * observe REACHABLE arp entry for A1 is now PERMANENT
    * delete vm and port
    * create port P2 with address A1 and create vm on node C1 with this port
    * vm is unreachable since arp cache contains PERMANENT entry for old port P1 mac/ip combo

  If I don't restart the l3-agent, once I have deleted the port it's arp
  entry does REACHABLE -> STALE and will either be replaced or timeout
  as expected but once it is set to PERMANENT it will never disappear
  which means any future use of that ip address (by a port with a
  different mac) will not work until that entry is manually deleted.

  [Where problems could occur]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1916761/+subscriptions