** Also affects: neutron (Ubuntu)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: neutron (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: neutron (Ubuntu Impish)
Status: New => Triaged
** Changed in: neutron (Ubuntu Jammy)
Status: New => Triaged
** Changed in: neutron (Ubuntu Impish)
Importance: Undecided => High
** Changed in: neutron (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: neutron (Ubuntu Kinetic)
Status: New => Triaged
** Changed in: neutron (Ubuntu Kinetic)
Importance: Undecided => High
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/zed
Importance: Undecided
Status: New
** Also affects: cloud-archive/yoga
Importance: Undecided
Status: New
** Also affects: cloud-archive/xena
Importance: Undecided
Status: New
** Changed in: cloud-archive/xena
Status: New => Triaged
** Changed in: cloud-archive/yoga
Status: New => Triaged
** Changed in: cloud-archive/zed
Status: New => Triaged
** Changed in: cloud-archive/yoga
Importance: Undecided => High
** Changed in: cloud-archive/xena
Importance: Undecided => High
** Changed in: cloud-archive/zed
Importance: Undecided => High
--
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 Ubuntu Cloud Archive:
Triaged
Status in Ubuntu Cloud Archive xena series:
Triaged
Status in Ubuntu Cloud Archive yoga series:
Triaged
Status in Ubuntu Cloud Archive zed series:
Triaged
Status in neutron:
Fix Released
Status in neutron package in Ubuntu:
Triaged
Status in neutron source package in Impish:
Triaged
Status in neutron source package in Jammy:
Triaged
Status in neutron source package in Kinetic:
Triaged
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/cloud-archive/+bug/1965297/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
