OVN: HA chassis group priority is different than gateway chassis priority
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
High
|
Rodolfo Alonso |
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:/
Bugzilla reference (OSP 17): https:/
tags: | added: ovn |
no longer affects: | kolla-ansible |
Changed in neutron: | |
assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
description: | updated |
no longer affects: | kolla-ansible/wallaby |
no longer affects: | kolla-ansible/xena |
no longer affects: | kolla-ansible/yoga |
no longer affects: | kolla-ansible/zed |
I don't have a deployment with baremetal servers but this looks like a legit bug.