Bug 2141657

Summary:	warning log appearing on VMs: found no SR-IOV networks
Product:	Container Native Virtualization (CNV)	Reporter:	Ram Lavi <ralavi>
Component:	Networking	Assignee:	Ram Lavi <ralavi>
Status:	CLOSED ERRATA	QA Contact:	Satyajit Bulage <sbulage>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.11.1	CC:	nrozen, phoracek, rnetser
Target Milestone:	---
Target Release:	4.11.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	bundle v4.11.2-2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2141654	Environment:
Last Closed:	2023-01-12 14:08:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ram Lavi 2022-11-10 11:48:31 UTC

+++ This bug was initially created as a clone of Bug #2141654 +++

Description of problem:
When creating a VMI, with no SRIOV interfaces, the log is filled with a warning log: 
found no SR-IOV networks to PCI-Address mapping. fall back to resource address pool.


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


How reproducible:


Steps to Reproduce:
1. Create a VMI with no SRIOV interfaces
2.
3.

Actual results:
virt-launcher logs show the warning logs every few seconds.

Expected results:
No such warning log to appear

Additional info:

--- Additional comment from Ram Lavi on 2022-11-10 11:45:45 UTC ---

https://github.com/kubevirt/kubevirt/pull/8754

Comment 1 Ram Lavi 2022-11-10 12:08:03 UTC

https://github.com/kubevirt/kubevirt/pull/8760

Comment 2 Petr Horáček 2022-11-24 09:08:06 UTC

Bumped on M/S via https://gitlab.cee.redhat.com/cpaas-midstream/openshift-virtualization/kubevirt/-/merge_requests/1111/diffs

Comment 4 Satyajit Bulage 2022-12-22 10:23:14 UTC

Verification Steps:
1. Created VM on SRIOV operator installed BM cluster.
2. VM is not using any SRIOV interfaces not the secondary one.
3. Observed virt-launcher pod logs for more than 20mins.
4. Also, checked logs via CLI
   i. oc logs virt-launcher-vm-example-spj4w -f | grep -i SRIOV

Conclusion: Warning log is not appearing in the virt-launcher pod of VMI.

Env: 
OCP-4.11.20
CNV-v4.11.2-10
SRIOV : 4.11.0-202208301406

Verifying Bug based on above conclusion.

Comment 11 errata-xmlrpc 2023-01-12 14:08:55 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 (OpenShift Virtualization 4.11.2 Images), 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/RHEA-2023:0155