Back to bug 2223916

Who When What Removed Added
Red Hat One Jira (issues.redhat.com) 2023-07-19 09:25:27 UTC Link ID Red Hat Issue Tracker OSP-26730
Eran Kuris 2023-07-20 07:30:16 UTC Severity unspecified medium
Roman Safronov 2023-07-20 15:12:11 UTC CC rsafrono
Roman Safronov 2023-07-20 16:04:03 UTC Comment 0 updated
Roman Safronov 2023-07-20 16:05:10 UTC Comment 0 is private 1 0
Maor 2023-07-23 16:45:26 UTC QA Contact ekuris mblue
CC mblue
Slawek Kaplonski 2023-07-26 10:37:22 UTC Keywords Triaged
Status NEW ON_DEV
Slawek Kaplonski 2023-07-26 10:37:48 UTC Assignee rhos-maint skaplons
Priority unspecified high
Slawek Kaplonski 2023-07-26 10:37:56 UTC Severity medium high
Eran Kuris 2023-07-27 13:41:00 UTC CC ekuris
Target Milestone --- z1
RHEL Program Management 2023-07-27 13:41:12 UTC Target Release --- 17.1
Slawek Kaplonski 2023-07-27 13:46:45 UTC Doc Text Cause: North-South traffic in vlan/flat tenant networks is distributed when Floating IPs are used.

Consequence: This is causing issue with Floating IP port forwardings associated with Neutron ports connected to the vlan or flat tenant networks as traffic to/from port forwardings needs to be centralized on the controller (networker) node.

Workaround (if any): To make Floating IP Port Forwarding to be working fine, either set "enable_distributed_floating_ip=False" in the Neutron configuration or use Geneve tenant networks intead of vlan/flat networks is required for now.

Result: Floating IP port forwarding will be working fine through centralized gateway node.
Doc Type If docs needed, set a value Known Issue
Slawek Kaplonski 2023-07-27 14:25:24 UTC Link ID OpenStack gerrit 2028846 Launchpad 2028846
Ian Frangs 2023-08-03 15:46:23 UTC Flags needinfo?(skaplons)
Slawek Kaplonski 2023-08-09 06:44:54 UTC Flags needinfo?(skaplons)
Greg Rakauskas 2023-08-09 16:25:09 UTC CC gregraka
Flags needinfo?(skaplons)
Doc Text Cause: North-South traffic in vlan/flat tenant networks is distributed when Floating IPs are used.

Consequence: This is causing issue with Floating IP port forwardings associated with Neutron ports connected to the vlan or flat tenant networks as traffic to/from port forwardings needs to be centralized on the controller (networker) node.

Workaround (if any): To make Floating IP Port Forwarding to be working fine, either set "enable_distributed_floating_ip=False" in the Neutron configuration or use Geneve tenant networks intead of vlan/flat networks is required for now.

Result: Floating IP port forwarding will be working fine through centralized gateway node.
In RHOSP 17.1 GA environments that use the ML2/OVN mechanism driver, there is a known issue with Networking service (neutron) ports connected to VLAN or flat project networks not properly forwarding floating IP (FIP) traffic. This problem is caused because VLAN and flat networks distribute north-south network traffic when FIPs are used, and instead FIP port forwarding should be centralized on the Controller or the Networker nodes.
+
Workaround: To resolve this problem and force FIP port forwarding through the centralized gateway node, either set `enable_distributed_floating_ip=false`, or use Geneve instead of VLAN or flat project networks.
Slawek Kaplonski 2023-08-10 07:24:43 UTC Flags needinfo?(skaplons)
Greg Rakauskas 2023-08-10 15:20:44 UTC Doc Text In RHOSP 17.1 GA environments that use the ML2/OVN mechanism driver, there is a known issue with Networking service (neutron) ports connected to VLAN or flat project networks not properly forwarding floating IP (FIP) traffic. This problem is caused because VLAN and flat networks distribute north-south network traffic when FIPs are used, and instead FIP port forwarding should be centralized on the Controller or the Networker nodes.
+
Workaround: To resolve this problem and force FIP port forwarding through the centralized gateway node, either set `enable_distributed_floating_ip=false`, or use Geneve instead of VLAN or flat project networks.
In RHOSP 17.1 GA environments that use the ML2/OVN mechanism driver, there is a known issue with floating IP port forwarding not working correctly. This problem is caused because VLAN and flat networks distribute north-south network traffic when FIPs are used, and, instead, FIP port forwarding should be centralized on the Controller or the Networker nodes.
+
Workaround: To resolve this problem and force FIP port forwarding through the centralized gateway node, either set the RHOSP Orchestration service (heat) parameter `NeutronEnableDVR` to `false`, or use Geneve instead of VLAN or flat project networks.
Flags needinfo?(skaplons)
Paul Grist 2023-08-11 13:37:00 UTC CC pgrist
Mike Burns 2023-08-11 13:59:33 UTC Target Milestone z1 z2
Mike Burns 2023-08-11 14:56:05 UTC Target Milestone z2 z1
Slawek Kaplonski 2023-08-16 07:06:27 UTC Link ID OpenStack gerrit 2028846
Slawek Kaplonski 2023-08-16 10:29:35 UTC Link ID OpenStack gerrit 889871
Slawek Kaplonski 2023-08-17 07:20:24 UTC Flags needinfo?(skaplons)

Back to bug 2223916