yahoo-eng-team team mailing list archive

[Oleg Bondarev <obondarev@xxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: High
     Assignee: Oleg Bondarev (obondarev)
         Status: New


** Tags: l2-pop

-- 
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:
  New

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