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

Bug 1975865

Summary:	Flaky test: NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy]
Product:	OpenShift Container Platform	Reporter:	Dan Winship <danw>
Component:	Networking	Assignee:	Andrew Stoycos <astoycos>
Networking sub component:	ovn-kubernetes	QA Contact:	Anurag saxena <anusaxen>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	medium
Priority:	medium	CC:	astoycos
Version:	4.9
Target Milestone:	---
Target Release:	4.9.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-07-30 15:06:51 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 Dan Winship 2021-06-24 15:22:24 UTC

The test

[sig-network] Netpol [LinuxOnly] NetworkPolicy between server and client should stop enforcing policies after they are deleted [Feature:NetworkPolicy] [Skipped:Network/OpenShiftSDN/Multitenant] [Skipped:Network/OpenShiftSDN] [Suite:openshift/conformance/parallel] [Suite:k8s]

assumes that after deleting a NetworkPolicy, the system will have been updated to reflect the new state within 3 seconds. This fails sometimes in CI, especially with ovn-kubernetes. The test needs to be fixed to do a retry loop (like every other NP test!)

Comment 1 Andrew Stoycos 2021-07-30 15:06:51 UTC

Closing this in favor of https://bugzilla.redhat.com/show_bug.cgi?id=1980141 Because I don't see this test flaking more than any of the others in CI. However the tests are flaky in our downstream so root cause needs to be continued. 

Also the test does retry, 

https://github.com/kubernetes/kubernetes/blob/master/test/e2e/network/netpol/network_policy.go#L894

It applies the policy runs ValidateOrFail (which has retrys built in), then deletes the policy and runs ValidateOrFail again. 

Thanks, 
Andrew

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