Bug 1813825

Summary: Namespace isolation fails due to race on neutron
Product: Red Hat OpenStack Reporter: Itzik Brown <itbrown>
Component: openstack-neutronAssignee: Rodolfo Alonso <ralonsoh>
Status: CLOSED CURRENTRELEASE QA Contact: Eran Kuris <ekuris>
Severity: urgent Docs Contact:
Priority: high    
Version: 16.0 (Train)CC: akatz, amuller, bhaley, chrisw, juriarte, njohnston, scohen, stchen
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-15.1.1-2.20200820054958.8ff90c2.el8ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-15 10:38:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Itzik Brown 2020-03-16 08:51:13 UTC 
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 9 stchen 2020-11-04 20:11:11 UTC 
Closing EOL, OSP 16.0 has been retired as of Oct 27, 2020
Comment 10 Brian Haley 2020-11-09 22:40:17 UTC 
Re-opening targeted at 16.1
Comment 13 Eran Kuris 2020-11-15 10:38:57 UTC 
closing because not relevant anymore for OSP16+ and OpenShift.