yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1928466@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Medium
     Assignee: Slawek Kaplonski (slaweq)
         Status: Confirmed


** Tags: l3-dvr-backlog

-- 
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:
  Confirmed

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