Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1932781

Summary: NetworkPolicies are not enforced immediately upon creation
Product: OpenShift Container Platform Reporter: Andy Bartlett <andbartl>
Component: NetworkingAssignee: Andrew Stoycos <astoycos>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: high CC: aconstan, astoycos
Version: 4.6   
Target Milestone: ---   
Target Release: 4.8.0   
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: 2021-05-07 14:10:46 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 Andy Bartlett 2021-02-25 09:09:01 UTC 
Description of problem:

My customer is seeing the following:

Our customer is experiencing a delay (of sometimes 10 minutes) between the creation of a NetworkPolicy and its enforcement. For example, when they create a NetworkPolicy and immediately a Pod thereafter, the Pod is not affected by a default deny egress rule. They're wondering whether Red Hat knows about this and/or has seen similar cases?

This cluster has 

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

OCP 4.6.16

How reproducible:

less than 100%

Steps to Reproduce:
1.
2.
3.

Actual results:

As mentioned above:

when they create a NetworkPolicy and immediately a Pod thereafter, the Pod is not affected by a default deny egress rule this can sometimes be up to 10 minutes.

Expected results:


Additional info:
Comment 5 Andrew Stoycos 2021-05-07 14:10:46 UTC 

*** This bug has been marked as a duplicate of bug 1950283 ***