Description of problem:
Please consider to include a note in FFU documentation like this [0] (Procedure #9) recommending to use address instead of devname to avoid issues after performing the Operating System upgrade. It could happen that device names change between OS versions. For example for ConnectX-5 cards and RHEL 8 we have these names (enp4s0fN):

~~~
[root@computedpdksriov-1 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.4 (Ootpa)
[root@computedpdksriov-1 ~]# lshw -c network -businfo
Bus info          Device      Class          Description
========================================================
pci@0000:04:00.0  enp4s0f0    network        MT27800 Family [ConnectX-5]
pci@0000:04:00.1  enp4s0f1    network        MT27800 Family [ConnectX-5]
~~~

After FFU, on the RHEL 9 compute we have have these names (enp4s0NpnN):

~~~
[root@computedpdksriov-0 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 9.2 (Plow)

[root@computedpdksriov-0 ~]# lshw -c network -businfo
Bus info          Device       Class          Description
=========================================================
pci@0000:04:00.0  enp4s0f0np0  network        MT27800 Family [ConnectX-5]
pci@0000:04:00.1  enp4s0f1np1  network        MT27800 Family [ConnectX-5]
~~~

If incorrect devnames are used the PciPassthroughFilter won't find the compute with incorrect names (the address does not change, so it is recommended to use it instead of devname)

[0] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1-beta/html/configuring_network_functions_virtualization/part-sriov-nfv-configuration#sect-configuring-sriov

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: