Bug 1510287
| Summary: | "virtlogd failed to connect to socket /run/dbus/system_bus_socket" logged when start a guest | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | yafu <yafu> |
| Component: | libvirt | Assignee: | Erik Skultety <eskultet> |
| Status: | CLOSED DUPLICATE | QA Contact: | Yanqiu Zhang <yanqzhan> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.5 | CC: | dyuan, fjin, rbalakri, thudziec, xuzhang, yafu, yanqzhan, zpeng |
| Target Milestone: | rc | Flags: | yanqzhan:
needinfo-
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-29 09:47:23 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
yafu
2017-11-07 06:30:54 UTC
*** Bug 1523187 has been marked as a duplicate of this bug. *** Can you still reproduce the issue with libvirt 4.3.0? Ping, can you still reproduce this issue with libvirt 4.5.0? I can't even reproduce with the original libvirt-3.9.0-1.el7.x86_64 in comment 0, or latest libvirt-4.4.0-2.el7.x86_64. yafu, are there any missing steps to reproduce it? Could you provide your test result pls if possible? 1.Try to reproduce: (1). Can reproduce with： kernel-3.10.0-768.el7.x86_64 qemu-kvm-rhev-2.10.0-21.el7_5.4.x86_64 libvirt-3.9.0-1.el7.x86_64 python-slip-dbus-0.4.0-4.el7.noarch dbus-libs-1.10.24-3.el7.x86_64 dbus-1.10.24-3.el7.x86_64 dbus-python-1.1.1-9.el7.x86_64 dbus-glib-0.100-7.el7.x86_64 selinux-policy-3.13.1-175.el7.noarch (2). Not reproduced after only update libvirt version: libvirt-3.9.0-14.el7_5.6.x86_64 ===================********=============================== Updated: libvirt.x86_64 0:3.9.0-14.el7_5.6 Dependency Updated: libvirt-client.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-config-network.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-config-nwfilter.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-interface.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-lxc.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-network.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-nodedev.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-nwfilter.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-qemu.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-secret.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage-core.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage-disk.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage-gluster.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage-iscsi.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage-logical.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage-mpath.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage-rbd.x86_64 0:3.9.0-14.el7_5.6 libvirt-daemon-driver-storage-scsi.x86_64 0:3.9.0-14.el7_5.6 libvirt-libs.x86_64 0:3.9.0-14.el7_5.6 ===================********=============================== (3). Also not reproduced after only update libvirt version to libvirt-4.4.0-2.el7.x86_64. 2. Latest testing: From part1, it seems that it only reproduces on the special match of kernel and libvirt. Then tested on latest rhel7.5 and rhel7.6 for the match. (1). RHEL7.5: latest kernel-3.10.0-862.el7.x86_64 and libvirt-3.9.0-14.el7_5.6.x86_64. ===> Not reproduced. (2). RHEL7.6: latest kernel-3.10.0-915.el7.x86_64 and libvirt-4.4.0-2.el7.x86_64. ===> Not reproduced. (In reply to yanqzhan from comment #6) > 1.Try to reproduce: > (1). Can reproduce with： > kernel-3.10.0-768.el7.x86_64 > qemu-kvm-rhev-2.10.0-21.el7_5.4.x86_64 > libvirt-3.9.0-1.el7.x86_64 > python-slip-dbus-0.4.0-4.el7.noarch > dbus-libs-1.10.24-3.el7.x86_64 > dbus-1.10.24-3.el7.x86_64 > dbus-python-1.1.1-9.el7.x86_64 > dbus-glib-0.100-7.el7.x86_64 > selinux-policy-3.13.1-175.el7.noarch > > (2). Not reproduced after only update libvirt version: > libvirt-3.9.0-14.el7_5.6.x86_64 > ===================********=============================== > Updated: > libvirt.x86_64 0:3.9.0-14.el7_5.6 > > > Dependency Updated: > libvirt-client.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-config-network.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-config-nwfilter.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-interface.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-lxc.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-network.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-nodedev.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-nwfilter.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-qemu.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-secret.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage-core.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage-disk.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage-gluster.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage-iscsi.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage-logical.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage-mpath.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage-rbd.x86_64 0:3.9.0-14.el7_5.6 > libvirt-daemon-driver-storage-scsi.x86_64 0:3.9.0-14.el7_5.6 > libvirt-libs.x86_64 0:3.9.0-14.el7_5.6 > ===================********=============================== > > (3). Also not reproduced after only update libvirt version to > libvirt-4.4.0-2.el7.x86_64. > > > > 2. Latest testing: > From part1, it seems that it only reproduces on the special match of kernel > and libvirt. Thanks for investigating this, the reason I asked about it was that libvirt 4-ish got a fix for a similar dbus issue, so I just wanted to make sure I can link the commit here and move the BZ to post. Fixed upstream by:
commit f94e5b215720c91c60219f1694783a603f0b619c
Refs: v4.3.0-rc1-1-gf94e5b2157
Author: Martin Kletzander <mkletzan>
AuthorDate: Thu Apr 26 12:17:03 2018 +0200
Commit: Martin Kletzander <mkletzan>
CommitDate: Thu Apr 26 17:40:57 2018 +0200
logging: Don't inhibit shutdown in system daemon
That is a job of libvirtd and virtlogd has a dependency on it, so that will
prevent it properly. Doing it one extra time in virtlogd might also cause AVC
denials because it is not allowed to call that dbus method.
Caused by commit df34363d58bb.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1547250
Signed-off-by: Martin Kletzander <mkletzan>
Reviewed-by: Daniel P. Berrangé <berrange>
*** This bug has been marked as a duplicate of bug 1547250 ***
|