← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1789846] Re: l2_pop flows missing when spawning VMs at a high rate

 

Reviewed:  https://review.openstack.org/598087
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=b32db30874a7729c4e9209cfc18e106a7e9fc697
Submitter: Zuul
Branch:    master

commit b32db30874a7729c4e9209cfc18e106a7e9fc697
Author: Oleg Bondarev <obondarev@xxxxxxxxxxxx>
Date:   Thu Aug 30 12:25:07 2018 +0400

    l2 pop: check for more than 1 first active port on a node
    
    With high concurrency more than 1 port may be activated on an
    OVS agent at the same time (like VM port + a DVR port),
    so the patch mitigates the condition by checking for 1 or 2
    first active ports.
    
    Given that the condition also contains "or self.agent_restarted(context)"
    which makes it True first 180 sec (by default) after agent restart,
    I believe the downside of changing 1 to 2 should be negligible.
    
    Please see bug for more details on the issue.
    
    Closes-Bug: #1789846
    Change-Id: Ieab0186cbe05185d47bbf5a31141563cf923f66f


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

Title:
  l2_pop flows missing when spawning VMs at a high rate

Status in neutron:
  Fix Released

Bug description:
  
  version: Pike, DVR enabled, 28 compute nodes
  scenario: spawn 140 VMs concurrently, with pre-created neutron ports
  issue: on some compute nodes VMs cannot get IP address, no reply on dhcp broadcasts. All new VMs spawned on the same compute node in the same network have this problem.

  it appears that flood table on compute nodes with issue is missing
  outputs to dhcp nodes:

   cookie=0x679aebcfbb8dc9a2, duration=296.991s, table=22, n_packets=2,
  n_bytes=220, priority=1,dl_vlan=4
  actions=strip_vlan,load:0x14->NXM_NX_TUN_ID[],output:"vxlan-
  ac1ef47a",output:"vxlan-ac1ef480",output:"vxlan-ac1ef46d",output
  :"vxlan-ac1ef477",...

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


References