Bug 2192913 - [OVN+VLAN+DVR] Flooded packets testing e/w with different tenant networks [Core OVN tracker]
Summary: [OVN+VLAN+DVR] Flooded packets testing e/w with different tenant networks [Co...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z4
: 17.1
Assignee: Jakub Libosvar
QA Contact: Candido Campos
URL:
Whiteboard:
Depends On: 2087779
Blocks: 2303550 2303551
TreeView+ depends on / blocked
 
Reported: 2023-05-03 13:47 UTC by Eduardo Olivares
Modified: 2025-04-03 04:25 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
This introduces an enhancement that you can configure to prevent flooding on the mesh between instances on different tenant networks. + Before this update, RHOSP environments with the OVN or OVS mechanism driver that had DVR enabled and used VLAN tenant networks, east/west traffic between instances connected to different tenant networks was flooded to the fabric. + To prevent this flooding in environments that use the OVN mechanism driver, you now can configure the parameter `OVNControllerGarpMaxTimeout` to control the frequency at which ovn-controller sends out out gratuitous ARP packets that announce MAC addresses of ports on VLAN tenant networks. + This parameter is not available in environments that use the OVS mechanism driver.
Clone Of:
: 2303550 2303551 (view as bug list)
Environment:
Last Closed: 2024-12-03 15:44:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FD-3233 0 None None None 2023-11-28 14:57:41 UTC
Red Hat Issue Tracker OSP-24725 0 None None None 2023-05-03 13:48:19 UTC
Red Hat Issue Tracker RHOSINFRA-5403 0 None None None 2023-11-28 16:13:05 UTC

Comment 28 Red Hat Bugzilla 2025-04-03 04:25:09 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


Note You need to log in before you can comment on or make changes to this bug.