yahoo-eng-team team mailing list archive

[OpenStack Infra <1928466@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/791492
Committed: https://opendev.org/openstack/neutron/commit/7b59b5069b1402730602b430416a15b1609253ea
Submitter: "Zuul (22348)"
Branch:    master

commit 7b59b5069b1402730602b430416a15b1609253ea
Author: Slawek Kaplonski <skaplons@xxxxxxxxxx>
Date:   Fri May 14 16:07:14 2021 +0200

    [DVR] Send allowed address pairs info to the L3 agents
    
    When new dvr router is going to be created on the node, L3 agent
    asks server for list of ports plugged to the subnets, to populate
    arp entries for all fixed IPs from those ports.
    There was missing info about allowed address pairs there, so those
    IPs were not populated in the qrouter namespace.
    Now it's added and L3 agent can add those arp entries to the qrouter
    namespaces too.
    
    Closes-Bug: #1928466
    Change-Id: I5d6c72c271ff450d9e43b3e33a99dd59d727882d


** 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/1928466

Title:
  Allowed address pairs aren't populated to the new host with DVR router

Status in neutron:
  Fix Released

Bug description:
  In the DVR routers, neutron-server needs to populate ARP entries also
  for IPs added to the ports as allowed address pairs. When e.g. new IP
  is added to the allowed address pairs of the port, it works fine and
  neutron server sends notification about such new arp entry to the all
  L3 agents where dvr router is placed.

  But in case when new vm plugged to the same router is spawned on
  completly new compute, or existing vm is migrated to the new compute
  where dvr router wasn't created before, arp entries for allowed
  address pairs aren't populated at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1928466/+subscriptions