yahoo-eng-team team mailing list archive

[Kevin Benton <1560464@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: neutron
     Importance: Undecided
     Assignee: Kevin Benton (kevinbenton)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => Kevin Benton (kevinbenton)

-- 
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:
  In Progress

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