Bug 1836212

Summary:	Long waiting timeouts while applying a policy
Product:	OpenShift Container Platform	Reporter:	Federico Paolinelli <fpaoline>
Component:	Networking	Assignee:	Peng Liu <pliu>
Networking sub component:	SR-IOV	QA Contact:	zhaozhanqi <zzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aconstan, anbhat, bbennett, pliu
Version:	4.5	Keywords:	UpcomingSprint
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1841063 (view as bug list)		Environment:
Last Closed:	2020-07-13 17:39:24 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:
Bug Depends On:
Bug Blocks:	1841063

Description Federico Paolinelli 2020-05-15 12:43:00 UTC

Description of problem:

Sometimes applying a policy takes longer than usual. 
This happens while running SR-IOV conformance test suite where a change can take up to 20 minutes. This seems to be related to the issue described in https://github.com/openshift/sriov-network-operator/pull/200


How reproducible:
Sporadic

Steps to Reproduce:
1. Run the sriov conformance test suite and check if a test fails for timeout

Comment 6 zhaozhanqi 2020-05-29 10:53:26 UTC

tried many time. and did not reproduced this issue. Move it to 'verified'

Comment 7 errata-xmlrpc 2020-07-13 17:39:24 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:2409