← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1965297] Re: l3ha don't set backup qg ports down

 

Reviewed:  https://review.opendev.org/c/openstack/neutron/+/834162
Committed: https://opendev.org/openstack/neutron/commit/36bf1df46df4de8f9ed0c19e1118480ce2e55d8a
Submitter: "Zuul (22348)"
Branch:    master

commit 36bf1df46df4de8f9ed0c19e1118480ce2e55d8a
Author: Edward Hope-Morley <edward.hope-morley@xxxxxxxxxxxxx>
Date:   Thu Mar 17 12:56:21 2022 +0000

    Partially revert "Do not link up HA router gateway in backup node"
    
    This partially reverts commit c52029c39aa824a67095fbbf9e59eff769d92587.
    
    We revert everything except one minor addition to
    neutron/agent/l3/ha_router.py which ensures that ha_confs path is
    created when the keepalived manager is initialised.
    
    Closes-Bug: #1965297
    Change-Id: I14ad015c4344b32f7210c924902dac4e6ad1ae88


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

Title:
  l3ha don't set backup qg ports down

Status in neutron:
  Fix Released

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



References