Bug 1831044

Summary: [OSP13] Namespace isolation fails due to race on neutron
Product: Red Hat OpenStack Reporter: Nate Johnston <njohnston>
Component: openstack-neutronAssignee: Rodolfo Alonso <ralonsoh>
Status: CLOSED CURRENTRELEASE QA Contact: Eran Kuris <ekuris>
Severity: medium Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: amuller, chrisw, fiezzi, juriarte, ltomasbo, mahmad, njohnston, nsatsia, peli, ralonsoh, rheinzma, scohen
Target Milestone: ---Keywords: TestOnly, Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-12.1.1-36.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-05 12:32:47 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 Nate Johnston 2020-05-04 14:12:32 UTC 
This bug was initially created as a copy of Bug #1813825

I am copying this bug because: 



Description of problem:
When trying to run a test on OCP on OSP environment the namespace isolation test fails (the connectivity between 2 namespaces succeeds when it shouldn't)

Version-Release number of selected component (if applicable):
2020-03-04.1

How reproducible:


Steps to Reproduce:
1. Create 2 namespaces with pod/service on each of them
2. Try to reach from the pod on one namespace the pod/service on another namespace
3.


Actual results:
The connectivity between 2 namespaces succeeds

Expected results:
The connectivity between 2 namespaces succeeds

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1688323
Comment 12 Lon Hohberger 2020-10-29 10:50:37 UTC 
According to our records, this should be resolved by openstack-neutron-15.1.1-0.20200701034713.bcea253.el7ost.  This build is available now.