Back to bug 1836998

Who When What Removed Added
James Smith 2020-05-19 16:26:20 UTC CC jamsmith
Doc Text Because of a core OVN bug, virtual machines with floating IP (FIP) addresses cannot route to other networks in an ML2/OVN deployment with distributed virtual routing (DVR) enabled. Core OVN sets a bad next hop when routing SNAT IPv4 traffic from a VM with a floating ip with DVR enabled. Instead of the gateway IP, OVN sets the destination IP. As a result, the router sends an ARP request for outer unknown IP instead of routing it to the gateway.
+
Before deploying a new overcloud with ML2/OVN, disable DVR by setting `NeutronEnableDVR: false` in an environment file.
+
If you have ML2/OVN in an existing deployment, perform the following steps:
+
. Set the enable_distributed_floating_ip parameter in the [ovs] section of neutron.conf to False
. Update the floating ip that requires external SNAT to work via Neutron API (e.g. by changing its description)
+
NOTE: Disabling DVR causes traffic to be centralized. All L3 traffic will go through the controller/network nodes. This may have an impact on scale, data plane performance and throughput.
Doc Type If docs needed, set a value Known Issue
James Smith 2020-05-19 19:32:24 UTC Doc Text Because of a core OVN bug, virtual machines with floating IP (FIP) addresses cannot route to other networks in an ML2/OVN deployment with distributed virtual routing (DVR) enabled. Core OVN sets a bad next hop when routing SNAT IPv4 traffic from a VM with a floating ip with DVR enabled. Instead of the gateway IP, OVN sets the destination IP. As a result, the router sends an ARP request for outer unknown IP instead of routing it to the gateway.
+
Before deploying a new overcloud with ML2/OVN, disable DVR by setting `NeutronEnableDVR: false` in an environment file.
+
If you have ML2/OVN in an existing deployment, perform the following steps:
+
. Set the enable_distributed_floating_ip parameter in the [ovs] section of neutron.conf to False
. Update the floating ip that requires external SNAT to work via Neutron API (e.g. by changing its description)
+
NOTE: Disabling DVR causes traffic to be centralized. All L3 traffic will go through the controller/network nodes. This may have an impact on scale, data plane performance and throughput.
Because of a core OVN bug, virtual machines with floating IP (FIP) addresses cannot route to other networks in an ML2/OVN deployment with distributed virtual routing (DVR) enabled. Core OVN sets a bad next hop when routing SNAT IPv4 traffic from a VM with a floating ip with DVR enabled. Instead of the gateway IP, OVN sets the destination IP. As a result, the router sends an ARP request for an unknown IP instead of routing it to the gateway.
+
Before deploying a new overcloud with ML2/OVN, disable DVR by setting `NeutronEnableDVR: false` in an environment file.
+
If you have ML2/OVN in an existing deployment, perform the following steps:
+
. Set the `enable_distributed_floating_ip parameter` in the [ovs] section of neutron.conf to False. You should also set `NeutronEnableDVR: false` in an environment file used in any re-deployments so that the next re-deployment does not re-enable DVR.
. Update the floating IP that requires external SNAT to work through the Neutron API (for example, by changing its description).
+
NOTE: Disabling DVR causes traffic to be centralized. All L3 traffic goes through the controller/network nodes. This may affect scale, data plane performance, and throughput.
lorenzo bianconi 2020-05-27 10:15:39 UTC Depends On 1840605
lorenzo bianconi 2020-05-31 22:19:37 UTC Depends On 1836976
Jakub Libosvar 2021-03-05 12:09:09 UTC Assignee amuller rhos-maint
Assaf Muller 2021-06-15 17:25:05 UTC CC amuller
Lon Hohberger 2021-07-09 16:28:33 UTC Assignee rhos-maint rhos-maint
Red Hat One Jira (issues.redhat.com) 2022-03-24 14:07:32 UTC Link ID Red Hat Issue Tracker OSP-5208
Eran Kuris 2023-07-18 10:44:23 UTC Status NEW CLOSED
Resolution --- WONTFIX
Last Closed 2023-07-18 10:44:23 UTC

Back to bug 1836998