Public bug reported: 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. ** 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/2100505 Title: Neutron OVN external ports creation change HA chassis group master Status in neutron: New 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 : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
