Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 1836998
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh94 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1836998
-
[OVN][DVR] Impossible to ping internet addresses from vm with FIP
Summary:
[OVN][DVR] Impossible to ping internet addresses from vm with FIP
Keywords
:
Regression
Tracking
Triaged
Status
:
CLOSED WONTFIX
Alias:
None
Product:
Red Hat OpenStack
Classification:
Red Hat
Component:
python-networking-ovn
Sub Component:
---
Version:
13.0 (Queens)
Hardware:
Unspecified
OS:
Unspecified
Priority:
urgent
Severity:
urgent
Target Milestone:
z12
Target Release
:
13.0 (Queens)
Assignee:
OSP Team
QA Contact:
Eran Kuris
Docs Contact:
URL:
Whiteboard:
Depends On:
1834433
1836976
1840605
Blocks:
TreeView+
depends on
/
blocked
Reported:
2020-05-18 15:44 UTC by
Jakub Libosvar
Modified:
2023-07-18 10:44 UTC (
History
)
CC List:
12 users
(
show
)
apevec
ctrautma
dalvarez
ekuris
jamsmith
jishi
jlibosva
lhh
lorenzo.bianconi
majopela
rsafrono
scohen
Fixed In Version:
Doc Type:
Known Issue
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 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.
Clone Of:
1836963
Environment:
Last Closed:
2023-07-18 10:44:23 UTC
Target Upstream Version:
Embargoed:
Attachments
(Terms of Use)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Red Hat Issue Tracker
OSP-5208
0
None
None
None
2022-03-24 14:07:31 UTC
Note
You need to
log in
before you can comment on or make changes to this bug.