yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #90691
[Bug 1995078] Fix included in openstack/kolla-ansible 13.7.0
This issue was fixed in the openstack/kolla-ansible 13.7.0 release.
** Changed in: kolla-ansible/xena
Status: Fix Committed => 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/1995078
Title:
OVN: HA chassis group priority is different than gateway chassis
priority
Status in kolla-ansible:
Fix Released
Status in kolla-ansible wallaby series:
Fix Committed
Status in kolla-ansible xena series:
Fix Released
Status in kolla-ansible yoga series:
Fix Released
Status in kolla-ansible zed series:
Fix Released
Status in neutron:
Confirmed
Bug description:
OpenStack release affected - Wallaby, Xena and Yoga for sure
OVN version: 21.12 (from CentOS NFV SIG repos)
Host OS: CentOS Stream 8
Neutron creates External ports for bare metal instances and uses ha_chassis_group.
Neutron normally defines a different priority for Routers LRP gateway chassis and ha_chassis_group.
I have a router with two VLANs attached - external (used for internet
connectivity - SNAT or DNAT/Floating IP) and internal VLAN network
hosting bare metal servers (and some Geneve networks for VMs).
If an External port’s HA chassis group active chassis is different
than gateway chassis (external vlan network) active chassis - those
bare metal servers have intermittent network connectivity for any
traffic going through that router.
In a thread on ovs-discuss ML - Numan Siddique wrote that "it is recommended that the
same controller which is actively handling the gateway traffic also
handles the external ports"
More information in this thread -
https://mail.openvswitch.org/pipermail/ovs-
discuss/2022-October/052067.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla-ansible/+bug/1995078/+subscriptions
References