← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1560464] Re: ovsdb monitor doesn't return ofport

 

Reviewed:  https://review.openstack.org/295753
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=62e88623d977d28c113a1e29458621f82d48f6e5
Submitter: Jenkins
Branch:    master

commit 62e88623d977d28c113a1e29458621f82d48f6e5
Author: Kevin Benton <kevin@xxxxxxxxxx>
Date:   Thu Mar 17 05:19:19 2016 -0700

    Watch for 'new' events in ovsdb monitor for ofport
    
    This adjusts the event handling logic in the ovs interface
    monitor to watch for 'new' events as well because this is
    when ofports are assigned to the interface. Previously we
    were only watching for 'insert' events, which would never
    include the ofport so this led to every port being skipped
    initially by the OVS agent and then picked up on the next
    polling interval.
    
    Closes-Bug: #1560464
    Change-Id: I46ac508a839c6db779323d5afb083f3425f96e87


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

Title:
  ovsdb monitor doesn't return ofport

Status in neutron:
  Fix Released

Bug description:
  The OVSDB monitor event parsing code does not get the ofport for a new
  port because the ofport isn't assigned until the 'new' action and it
  only pays attention to the 'insert' action.

  This leads to the event processing to think that the port is never
  ready on the first iteration so it gets put off until the next
  iteration where it directly polls the db to see if it is active. This
  adds the time configured for the polling interval to every new port
  wiring.

  
  Evidence of this can be seen in the logs with "Port <port-uuid> not ready yet on the bridge": http://logs.openstack.org/87/295487/1/check/gate-tempest-dsvm-neutron-full/5022853/logs/screen-q-agt.txt.gz#_2016-03-21_22_18_45_274

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


References