Bug 1964625 - NETID duplicate check is only required in NetworkPolicy Mode
Summary: NETID duplicate check is only required in NetworkPolicy Mode
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Mohamed Mahmoud
QA Contact: zhaozhanqi
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-25 19:20 UTC by Mohamed Mahmoud
Modified: 2021-07-27 23:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2021-07-27 23:10:08 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift sdn pull 307 0 None open Bug 1964625: NETID duplicate check is only required in NetworkPolicy Mode 2021-05-25 20:28:47 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 23:10:22 UTC

Description Mohamed Mahmoud 2021-05-25 19:20:20 UTC
Description of problem:

Bug 1928851: prevent manually creating netns with existing NetID, however that logic should be limited to NetworkPolicy mode, its acceptable to have duplicate 
in MutliTenant mode.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 3 zhaozhanqi 2021-06-01 09:50:45 UTC
Verified this bug on 4.8.0-0.nightly-2021-06-01-002052

for multitenant mode, when join-network oc adm pod-network join-projects --to=z1 z2, pods can communicated with each other in z1 and z2

Move this to verified.

Comment 6 errata-xmlrpc 2021-07-27 23:10:08 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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.

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


Note You need to log in before you can comment on or make changes to this bug.