Bug 1520363

Summary: The pod should not be able to access external when the egressIP set to multiple netns
Product: OpenShift Container Platform Reporter: Meng Bo <bmeng>
Component: NetworkingAssignee: Dan Winship <danw>
Status: CLOSED ERRATA QA Contact: Meng Bo <bmeng>
Severity: low Docs Contact:
Priority: medium    
Version: 3.7.0CC: aos-bugs, atragler, bbennett
Target Milestone: ---   
Target Release: 3.10.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-30 19:09:00 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:
Description Flags
openflow_dump_on_both_node none

Description Meng Bo 2017-12-04 11:11:55 UTC
Created attachment 1362632 [details]

Description of problem:
Add the egressIP which is holding by any node to multiple netns. The pod in the project should loss the external access.

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

How reproducible:

Steps to Reproduce:
1. Setup multinode env with multitenant or networkpolicy plugin

2. Add the egressIP to any of the node
oc patch hostsubnet node1 -p "{\"egressIPs\":[\"$EGRESS_IP\"]}"

3. Assign the egressIP above to multiple netns
oc patch netnamespace project1 -p "{\"egressIPs\":[\"$EGRESS_IP\"]}"
oc patch netnamespace project2 -p "{\"egressIPs\":[\"$EGRESS_IP\"]}"

4. Create pod in all of the projects and try to access the outside

Actual results:
The pod in the first project can access external network through the egressIP.
The pod in the second project can access external network through the node IP.

Expected results:
All the pods in both projects should not be able to access external network.

Additional info:

Comment 1 Dan Winship 2018-03-02 15:33:33 UTC

Comment 2 Dan Winship 2018-05-21 12:00:15 UTC
oops, this never got bumped to MODIFIED, but it's been fixed for a while now...

Comment 4 Meng Bo 2018-06-07 09:11:46 UTC
Issue has been fixed on v3.10.0-0.58.0

Comment 6 errata-xmlrpc 2018-07-30 19:09:00 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, and where to find the updated
files, follow the link below.

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