Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionyalzhang@redhat.com
2018-07-24 11:17:38 UTC
Description of problem:
there is error like "virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL" promoted once the vm is failed to start
Version-Release number of selected component (if applicable):
libvirt-4.5.0-4.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. set libvirtd log
# rm -fr /var/log/libvirt/libvirtd.log
append below settings into /etc/libvirt/libvirtd.conf
log_level=2
log_outputs='2:file:/var/log/libvirt/libvirtd.log'
2. restart libvirtd
# systemctl restart libvirtd
# grep error /var/log/libvirt/libvirtd.log
3. make some changes, to let the vm fail to start, such as:
# virsh net-destroy default
Network default destroyed
# virsh dumpxml rhel | grep /interface -B5
<interface type='network'>
<mac address='52:54:00:9b:f2:25'/>
<source network='default'/>
<model type='rtl8139'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
</interface>
# virsh start rhel
error: Failed to start domain rhel
error: Requested operation is not valid: network 'default' is not active
4. check the libvirtd log, there is error about nwfilter
# grep error /var/log/libvirt/libvirtd.log
2018-07-24 11:05:38.015+0000: 7174: error : virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL
Scenario B:
edit the images to non-exists ones:
# virsh dumpxml rhel | grep /disk -B6
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/var/lib/libvirt/non-exists/RHEL-7.6-x86_64-latest.qcow2'/>
...
</disk>
# virsh start rhel
error: Failed to start domain rhel
error: Cannot access storage file '/var/lib/libvirt/non-exists/RHEL-7.6-x86_64-latest.qcow2' (as uid:107, gid:107): No such file or directory
# grep error /var/log/libvirt/libvirtd.log
2018-07-24 11:09:14.947+0000: 27080: error : virStorageFileReportBrokenChain:4656 : Cannot access storage file '/var/lib/libvirt/non-exists/RHEL-7.6-x86_64-latest.qcow2' (as uid:107, gid:107): No such file or directory
2018-07-24 11:09:14.949+0000: 27080: error : virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL
Scenario C:
set vm with non-exists nwfiler
# virsh dumpxml rhel | grep /interface -B6
<interface type='network'>
<mac address='52:54:00:9b:f2:25'/>
<source network='default'/>
<model type='rtl8139'/>
<filterref filter='no-exists'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/>
</interface>
# virsh start rhel
error: Failed to start domain rhel
error: internal error: referenced filter 'no-exists' is missing
# grep error /var/log/libvirt/libvirtd.log
2018-07-24 11:12:54.141+0000: 17114: error : virNWFilterObjListFindInstantiateFilter:201 : internal error: referenced filter 'no-exists' is missing
2018-07-24 11:12:54.164+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device
2018-07-24 11:12:54.173+0000: 17114: error : virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL
2018-07-24 11:12:54.174+0000: 17114: error : virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL
2018-07-24 11:12:54.176+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device
2018-07-24 11:12:54.179+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device
2018-07-24 11:12:54.181+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device
2018-07-24 11:12:54.183+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device
2018-07-24 11:12:54.193+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device
2018-07-24 11:12:54.198+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device
2018-07-24 11:12:54.200+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device
Actual results:
there is error about nwfilter when fail to start mv
Expected results:
there should be no such error
Additional info:
Comment 2yalzhang@redhat.com
2018-07-24 11:19:01 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/RHSA-2018:3113
Description of problem: there is error like "virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL" promoted once the vm is failed to start Version-Release number of selected component (if applicable): libvirt-4.5.0-4.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. set libvirtd log # rm -fr /var/log/libvirt/libvirtd.log append below settings into /etc/libvirt/libvirtd.conf log_level=2 log_outputs='2:file:/var/log/libvirt/libvirtd.log' 2. restart libvirtd # systemctl restart libvirtd # grep error /var/log/libvirt/libvirtd.log 3. make some changes, to let the vm fail to start, such as: # virsh net-destroy default Network default destroyed # virsh dumpxml rhel | grep /interface -B5 <interface type='network'> <mac address='52:54:00:9b:f2:25'/> <source network='default'/> <model type='rtl8139'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </interface> # virsh start rhel error: Failed to start domain rhel error: Requested operation is not valid: network 'default' is not active 4. check the libvirtd log, there is error about nwfilter # grep error /var/log/libvirt/libvirtd.log 2018-07-24 11:05:38.015+0000: 7174: error : virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL Scenario B: edit the images to non-exists ones: # virsh dumpxml rhel | grep /disk -B6 <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/non-exists/RHEL-7.6-x86_64-latest.qcow2'/> ... </disk> # virsh start rhel error: Failed to start domain rhel error: Cannot access storage file '/var/lib/libvirt/non-exists/RHEL-7.6-x86_64-latest.qcow2' (as uid:107, gid:107): No such file or directory # grep error /var/log/libvirt/libvirtd.log 2018-07-24 11:09:14.947+0000: 27080: error : virStorageFileReportBrokenChain:4656 : Cannot access storage file '/var/lib/libvirt/non-exists/RHEL-7.6-x86_64-latest.qcow2' (as uid:107, gid:107): No such file or directory 2018-07-24 11:09:14.949+0000: 27080: error : virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL Scenario C: set vm with non-exists nwfiler # virsh dumpxml rhel | grep /interface -B6 <interface type='network'> <mac address='52:54:00:9b:f2:25'/> <source network='default'/> <model type='rtl8139'/> <filterref filter='no-exists'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </interface> # virsh start rhel error: Failed to start domain rhel error: internal error: referenced filter 'no-exists' is missing # grep error /var/log/libvirt/libvirtd.log 2018-07-24 11:12:54.141+0000: 17114: error : virNWFilterObjListFindInstantiateFilter:201 : internal error: referenced filter 'no-exists' is missing 2018-07-24 11:12:54.164+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device 2018-07-24 11:12:54.173+0000: 17114: error : virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL 2018-07-24 11:12:54.174+0000: 17114: error : virNWFilterBindingLookupByPortDev:589 : portdev in virNWFilterBindingLookupByPortDev must not be NULL 2018-07-24 11:12:54.176+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device 2018-07-24 11:12:54.179+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device 2018-07-24 11:12:54.181+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device 2018-07-24 11:12:54.183+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device 2018-07-24 11:12:54.193+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device 2018-07-24 11:12:54.198+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device 2018-07-24 11:12:54.200+0000: 17253: error : virNetDevSendEthtoolIoctl:3072 : ethtool ioctl error: No such device Actual results: there is error about nwfilter when fail to start mv Expected results: there should be no such error Additional info: