Bug 1838001

Summary:	Namespace isolation fails due to Sg remote_group_id usage
Product:	OpenShift Container Platform	Reporter:	Luis Tomas Bolivar <ltomasbo>
Component:	Networking	Assignee:	Luis Tomas Bolivar <ltomasbo>
Networking sub component:	kuryr	QA Contact:	Jon Uriarte <juriarte>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	unspecified	CC:	juriarte
Version:	3.11.0
Target Milestone:	---
Target Release:	3.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-28 05:44:13 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 Luis Tomas Bolivar 2020-05-20 11:04:40 UTC

When deploying OCP (3.11) on OSP (13) environment the namespace isolation is not enforced since the connectivity between 2 namespaces succeeds when it shouldn't.

This happens due to the usage of remote_group_id at Neutron Security groups which is affected by this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1831044

Kuryr should avoid the usage of remote_group_id and use remote_ip_prefix instead on its security groups

Comment 3 Jon Uriarte 2020-05-22 15:07:52 UTC

Verified in openshift-ansible-3.11.219 (2020-05-20.1) on top of OSP 13 2020-05-19.2.

Namespace isolation is working as expected, tempests namespace isolation tests pass
and manual tests as well.
Could not reproduce the issue described in https://bugzilla.redhat.com/show_bug.cgi?id=1831044

The security groups openshift-ansible-openshift.example.com-allow_from_default,
openshift-ansible-openshift.example.com-allow_from_namespace, and the ones belonging to load
balancer's ports do not have a Remote Security Group .

Comment 5 errata-xmlrpc 2020-05-28 05:44:13 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.

https://access.redhat.com/errata/RHBA-2020:2215