openstack/neutron
Code Issues Proposed changes

Add release note with known issue with FIP PFs and vlan tenant networks

Browse Source 
This patch adds just release note with the known issue to describe known
wrong configuration which cause FIP Port Forwarding to not work properly
in ML2/OVN backend and distributed FIPs enabled.
For more details, please check related bug.

Related-bug: #2028846
Change-Id: I48b5358f4c3ac492d68b00a4c0153370332e9249
This commit is contained in:
Slawek Kaplonski 2023-09-12 16:02:02 +02:00 committed by Brian Haley
parent 8cba9a2ee8
commit b2ceb8b854
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
releasenotes/notes/Known-incompatibility-in-the-OVN-L3-with-FIP-PF-and-distributed-FIPs-config-0b4e9a92255cf4a8.yaml Normal file
View File

@ -0,0 +1,13 @@
---
issues:
- |
When ``ML2/OVN`` backend and it's L3 service plugin (``ovn-router``) are
used together with "vlan" or "flat" network types used as tenant network
type, floating IP port forwarding (FIP PF) will not work if distributed
Floating IPs are enabled (``enable_distributed_floating_ip`` = ``True``).
To workaround this issue one of the following changes needs to be done:
* tunnel networks ("geneve" or "vxlan") should be used as tenant network types or
* Floating IPs should be centralized (``enable_distributed_floating_ip`` = ``False``).
For more details see `bug 2028846 <https://bugs.launchpad.net/neutron/+bug/2028846>`_.