Bug 1883214

Summary: Port flooding of packets on br-int causing other VMs to get traffic from neighbours - tripleo integration
Product: Red Hat OpenStack Reporter: Bernard Cafarelli <bcafarel>
Component: puppet-neutronAssignee: Bernard Cafarelli <bcafarel>
Status: CLOSED ERRATA QA Contact: Candido Campos <ccamposr>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: astupnik, beagles, cylopez, fsoppels, jjoyce, jschluet, shtiwari, skaplons, slinaber, tvignaud
Target Milestone: z14Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-neutron-12.4.1-13.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-16 13:55:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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