From 8aff176d319d021ce759fd049e6fceeb68ed3782 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Mon, 9 Dec 2024 06:29:07 -0800 Subject: [PATCH] docs: mention bug 1995078 Change-Id: I143e822c0fe42e231dfe3c4fe72177607489dad6 --- doc/source/admin/ovn-networking.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/source/admin/ovn-networking.rst b/doc/source/admin/ovn-networking.rst index a2af7a38d8..8305a1b19b 100644 --- a/doc/source/admin/ovn-networking.rst +++ b/doc/source/admin/ovn-networking.rst @@ -143,6 +143,18 @@ This can be configured manually, but *should* (as far as Ironic is aware) be configured by Neutron and set on interfaces matching the bridge mappings. At least, it works that way in Devstack. +Outbound SNAT +------------- + +Outbound connectivity (that traverses the Neutron/OVN router) is known to be problematic +due to a bug in the way External port priority is handled differently than port assignment +than the Chassis Gateway, the very same mentioned previously. Ultimately this can create +a mismatch between the ports and results in intermittent traffic loss. A known workaround +is to manually update the HA Chassis Group and Gateway Chassis priorities so these are in sync +for a given Neutron network and associated router. + +This is being tracked as `bug 1995078 `_. + ML2 Plugins -----------