Bug 1883214 - Port flooding of packets on br-int causing other VMs to get traffic from neighbours - tripleo integration
Summary: Port flooding of packets on br-int causing other VMs to get traffic from neig...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-neutron
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z14
: 13.0 (Queens)
Assignee: Bernard Cafarelli
QA Contact: Candido Campos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-28 13:07 UTC by Bernard Cafarelli
Modified: 2024-06-13 23:10 UTC (History)
10 users (show)

Fixed In Version: puppet-neutron-12.4.1-13.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-16 13:55:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 755233 0 None MERGED Add agent/explicitly_egress_direct support 2020-12-13 20:46:03 UTC
Red Hat Issue Tracker OSP-32283 0 None None None 2024-06-13 23:10:51 UTC
Red Hat Product Errata RHBA-2020:5575 0 None None None 2020-12-16 13:55:26 UTC

Description Bernard Cafarelli 2020-09-28 13:07:03 UTC 
This bug was initially created as a copy of Bug #1841194

I am copying this bug because: 
we need to add support for this new option in puppet-neutron, in ovs agent configuration [agent] section:
# When set to True, the accepted egress unicast traffic will not use action
# NORMAL. The accepted egress packets will be taken care of in the final egress
# tables direct output flows for unicast traffic. (boolean value)
#explicitly_egress_direct = false

Once added in puppet-neutron, this can then enabled in THT template with something similar to:
  ComputeExtraConfig:
    neutron::agents::ml2::ovs::explicitly_egress_direct: True
Comment 23 errata-xmlrpc 2020-12-16 13:55:05 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 13.0 director bug fix advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:5575
Note You need to log in before you can comment on or make changes to this bug.