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

Bug 1834371

Summary:	Unable to run SRIOV conformance tests
Product:	OpenShift Container Platform	Reporter:	Sebastian Scheinkman <sscheink>
Component:	Networking	Assignee:	Federico Paolinelli <fpaoline>
Networking sub component:	SR-IOV	QA Contact:	Nikita <nkononov>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	zzhao
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:37:32 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 Sebastian Scheinkman 2020-05-11 15:25:14 UTC

Description of problem:
All the sriov conformance test are failing

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


How reproducible:
100%

Steps to Reproduce:
1. Deploy sriov operator
2. Run the e2e conformance tests


Additional info:
The tests are failing because of two changes:
1. There was a change in the log output of the sriov config daemon
2. There was a change in the cnf-utils image

Comment 3 zhaozhanqi 2020-05-26 06:40:39 UTC

hi, Sebastian

Could you share the cnf ci job or could you help assigned cnf QE to verified this bug? thanks

Comment 4 Sebastian Scheinkman 2020-05-26 07:31:15 UTC

(In reply to zhaozhanqi from comment #3)
> hi, Sebastian
> 
> Could you share the cnf ci job or could you help assigned cnf QE to verified
> this bug? thanks

Sure I move it to our CNF-network QE

Thanks!

Comment 5 zhaozhanqi 2020-06-19 02:52:09 UTC

Move this bug to 'verified' according to https://bugzilla.redhat.com/show_bug.cgi?id=1840160#c3

Comment 6 errata-xmlrpc 2020-07-13 17:37:32 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