yahoo-eng-team team mailing list archive

[OpenStack Infra <1866068@xxxxxxxxxxxxxxxxxx>]

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

commit d7c23431ad3959eb5fd74e42ea95d446e4e7566d
Author: Jakub Libosvar <libosvar@xxxxxxxxxx>
Date:   Wed Mar 18 14:27:17 2020 +0000

    [ovn]: Create neutron_pg_drop Port Group on init
    
    The patch adds a short living connection in pre-fork routine that
    creates neutron_pg_drop Port Group. Later after workers are spawned,
    each worker also creates a short living connection and waits for an
    event that the Port Group was created.
    
    The short living IDLs limit its tables only for relevant tables so it
    doesn't fetch the whole OVS DB to the local copy.
    
    Closes-bug: #1866068
    
    Change-Id: I1f5af36b8c3d5650f890edfed3c33dc206869824
    Signed-off-by: Jakub Libosvar <libosvar@xxxxxxxxxx>


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

Title:
  [OVN] neutron_pg_drop port group table creation race condition

Status in neutron:
  Fix Released

Bug description:
  With HA controllers, when first two ports are created simultaneously
  and each request is picked by a different neutron-server, it can
  happen one port fails the creation because it fails creating
  neutron_pg_drop port group entry in OVN.

  This is because neutron_pg_drop entry is unique in the whole cloud and
  is created on the first attempt of port creation, if it doesn't exist.

  The solution can be creating the entry during server start.

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