yahoo-eng-team team mailing list archive

[Edward Hope-Morley <1965297@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The history to this request is as follows; bug 1916024 fixed an issue
that subsequently had to be reverted due to a regression that it
introduced (see bug 1927868) and the original issue can once again
present itself in that keepalived is unable to send GARP on the qg port
until the port is marked as UP by neutron which in loaded environments
can sometimes take longer than keepalived will wait (e.g. when an
l3-agent is restarted on a host that has hundreds of routers). The
reason why qg- ports are marked as DOWN is because of the patch landed
as part of bug 1859832 and as I understand it there is now consensus
from upstream [1] to revert that patch as well and a better solution is
needed to fix that particular issue. I have not found a bug open yet for
the revert hence why I am opening this one.

[1]
https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-03-04-14.03.log.txt

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1965297

Title:
  l3ha don't set backup qg ports down

Status in neutron:
  New

Bug description:
  The history to this request is as follows; bug 1916024 fixed an issue
  that subsequently had to be reverted due to a regression that it
  introduced (see bug 1927868) and the original issue can once again
  present itself in that keepalived is unable to send GARP on the qg
  port until the port is marked as UP by neutron which in loaded
  environments can sometimes take longer than keepalived will wait (e.g.
  when an l3-agent is restarted on a host that has hundreds of routers).
  The reason why qg- ports are marked as DOWN is because of the patch
  landed as part of bug 1859832 and as I understand it there is now
  consensus from upstream [1] to revert that patch as well and a better
  solution is needed to fix that particular issue. I have not found a
  bug open yet for the revert hence why I am opening this one.

  [1]
  https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-03-04-14.03.log.txt

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