+++ This bug was initially created as a clone of Bug #1948647 +++ Description of problem: Whenever nova binds an instance to a VF, as in an SR-IOV deployment, then you get this message in nova-compute.log: 2021-04-07 15:13:21.762 6 WARNING nova.pci.utils [req-29028659-fc7a-414b-8e57-31c23e894c22 - - - - -] No net device was found for VF 0000:3b:02.1: nova.exception.PciDeviceNotFoundById: PCI device 0000:3b:02.1 not found Version-Release number of selected component (if applicable): 16.x How reproducible: 100% See the launchpad bug: https://bugs.launchpad.net/nova/+bug/1808738 This WARNING message is a source of confusion for customers and support. Some are presuming that this message explains other issues they are experiencing. See support case 02821308, 02465751, 02183767, 02518517 Can we change the log level of that message to DEBUG? --- Additional comment from melanie witt on 2021-04-14 17:12:39 UTC --- We discussed this bug on the triage call today and agreed to change the location of this message from the periodic task to init_host so that it's only emitted once at startup. We'll also add more text to the message to explain what an operator should check and under what circumstance they should check it. And depending on feedback during code review, we might change the log level of the message to INFO -- we will start with keeping it at WARNING with the additional text so operators know when to be concerned about it, but if review consensus is that WARNING level would cause unnecessary alarm, we might go with INFO. We think we don't want to use DEBUG because it would most likely be completely hidden in a production deployment and operators would miss the warning about a potential problem in the deployment.
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 (Release of components for Red Hat OpenStack Platform 16.2.4), 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-2022:8794