yahoo-eng-team team mailing list archive

[OpenStack Infra <1808136@xxxxxxxxxxxxxxxxxx>]

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

commit 3995abefb16181594181133b271cdf35fa8d9937
Author: Oleg Bondarev <obondarev@xxxxxxxxxxxx>
Date:   Wed Dec 12 15:11:43 2018 +0400

    Do state report after setting start_flag on OVS restart
    
    This fixes race condition leading to lack of fdb entries
    on agent after OVS restart, if agent managed to handle all ports
    before sending state report with start_flag set to True.
    
    Change-Id: I943f8d805630cdfbefff9cff1fb4bce89210618b
    Closes-Bug: #1808136


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

Title:
  l2 pop doesn't always provide the whole list of fdb entries on OVS
  restart

Status in neutron:
  Fix Released

Bug description:
  bug https://bugs.launchpad.net/neutron/+bug/1804842 was fixed, but
  there is still a race condition, which leads to the same issue:

  success scenario:
   - OVS is restarted
   - agent start_flag set to True
   - report state done
   - ports updated, server sends fdb entries as it sees agent as restarted

  fail scenario:
   - OVS is restarted
   - agent start_flag set to True
   - ports updated, server doesn't send fdb entries as report state with start flag has not yet come
   - report state done
   - no fdb entries on agent (since no update port messages to server within config.agent_boot_time sec)

  The proposal is to force state report right after setting start_flag.
  No side effects expected.

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