Bug 1600468
Summary: | domifaddr should not query non-existing file for interface from host bridge network | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Fangge Jin <fjin> |
Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
Status: | CLOSED ERRATA | QA Contact: | yalzhang <yalzhang> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.6 | CC: | dyuan, lmen, xuzhang, yalzhang |
Target Milestone: | rc | Keywords: | Upstream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libvirt-4.5.0-5.el7 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-10-30 09:58:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Fangge Jin
2018-07-12 10:37:43 UTC
Patch proposed upstream: https://www.redhat.com/archives/libvir-list/2018-July/msg01756.html test on libvirt-4.5.0-5.virtcov.el7.x86_64, the bug is fixed. # virsh domiflist rhel Interface Type Source Model MAC ------------------------------------------------------- net_target network default rtl8139 52:54:00:d5:e3:68 user_target user - rtl8139 52:54:00:9e:c8:e9 udp_target udp - rtl8139 52:54:00:22:c9:42 mcast_target mcast - rtl8139 52:54:00:93:db:5e bridge_target bridge br0 rtl8139 52:54:00:1e:a3:ae # virsh domifaddr rhel Name MAC address Protocol Address ------------------------------------------------------------------------------- net_target 52:54:00:d5:e3:68 ipv4 192.168.122.80/24 # virsh domifaddr rhel bridge_target Name MAC address Protocol Address ------------------------------------------------------------------------------- Check log file and found no error in libvirtd.log Also test bridge type interface connected to ovs bridge, no error like comment 0. 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 |