Reviewed: https://review.opendev.org/c/openstack/neutron/+/943689
Committed:
https://opendev.org/openstack/neutron/commit/978d0b7bfbe156098fc6ed017a6fb0e02483a268
Submitter: "Zuul (22348)"
Branch: master
commit 978d0b7bfbe156098fc6ed017a6fb0e02483a268
Author: Rodolfo Alonso Hernandez <ralon...@redhat.com>
Date: Fri Mar 7 11:31:59 2025 +0000
[OVN] Retrieve the HA_Chassis_Group in ``_sync_ha_chassis_group``
Instead of calling the method ``ha_chassis_group_add`` that is not
returning the existing HA_Chassis_Group register if present, this patch
is first retrieving it from the database. If the register is not
present, then a creation call is issued.
Closes-Bug: #2100505
Change-Id: I8b190f41e8a83e47ea64b1b2962fbca49fbc5f63
** 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/2100505
Title:
Neutron OVN external ports creation change HA chassis group master
Status in neutron:
Fix Released
Bug description:
Openstack Version: 2024.2
When a neutron OVN external port is created the _sync_ha_chassis_group
https://opendev.org/openstack/neutron/src/commit/ec257eb74a64e3782c052f975942e17ba085eeb3/neutron/common/ovn/utils.py#L1098
is called, if the HA Chassis group is already present the function is
supposed to keep the chassis with the maximum priority untouched to
avoid recreation of the ports on another chassis.
This is not the case since the ha_ch_grp_cmd.result is never populated
even if the ha chassis group is present.
I added a functional test to prove this behavior
https://review.opendev.org/c/openstack/neutron/+/942901.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2100505/+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
