Bug 2141657 - warning log appearing on VMs: found no SR-IOV networks
Summary: warning log appearing on VMs: found no SR-IOV networks
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 4.11.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.11.2
Assignee: Ram Lavi
QA Contact: Satyajit Bulage
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-10 11:48 UTC by Ram Lavi
Modified: 2023-01-12 14:09 UTC (History)
3 users (show)

Fixed In Version: bundle v4.11.2-2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2141654
Environment:
Last Closed: 2023-01-12 14:08:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 8754 0 None Merged [release-0.58] hostdev: Avoid creating SR-IOV pool when not configured 2022-11-24 09:08:05 UTC
Red Hat Issue Tracker CNV-22394 0 None None None 2022-11-10 11:59:47 UTC
Red Hat Product Errata RHEA-2023:0155 0 None None None 2023-01-12 14:09:12 UTC

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 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


Note You need to log in before you can comment on or make changes to this bug.