The symptoms sound very much like the behavior in the old linked Redhat bug. The only changes applied to the system prior to this behavior starting were the following package upgrades. 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: dbus-libs-1:1.14.8-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: libxcrypt-4.4.35-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: dbus-tools-1:1.14.8-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: pyproject-srpm-macros-1.9.0-1.fc38.noarch 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: pyproject-rpm-macros-1.9.0-1.fc38.noarch 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: dbus-common-1:1.14.8-1.fc38.noarch 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: dbus-daemon-1:1.14.8-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: dbus-1:1.14.8-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: gnome-maps-44.2-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: dbus-x11-1:1.14.8-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: libxcrypt-compat-4.4.35-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: libxcrypt-devel-4.4.35-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: dbus-devel-1:1.14.8-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: python3-argcomplete-2.0.0-8.fc38.noarch 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: ocl-icd-2.3.2-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: ibus-libpinyin-1.15.3-2.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: epiphany-runtime-1:44.3-1.fc38.x86_64 2023-06-07T19:47:22-0700 SUBDEBUG Upgrade: container-selinux-2:2.218.0-1.fc38.noarch 2023-06-07T19:47:33-0700 SUBDEBUG Upgrade: libxcrypt-4.4.35-1.fc38.i686 2023-06-07T19:47:33-0700 SUBDEBUG Upgrade: dbus-libs-1:1.14.8-1.fc38.i686 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: libxcrypt-devel-4.4.34-1.fc38.x86_64 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: dbus-devel-1:1.14.6-1.fc38.x86_64 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: pyproject-rpm-macros-1.8.0-1.fc38.noarch 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: pyproject-srpm-macros-1.8.0-1.fc38.noarch 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: python3-argcomplete-2.0.0-6.fc38.noarch 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: libxcrypt-4.4.34-1.fc38.i686 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: dbus-libs-1:1.14.6-1.fc38.i686 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: container-selinux-2:2.216.0-1.fc38.noarch 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: dbus-x11-1:1.14.6-1.fc38.x86_64 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: dbus-daemon-1:1.14.6-1.fc38.x86_64 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: dbus-tools-1:1.14.6-1.fc38.x86_64 2023-06-07T19:47:33-0700 SUBDEBUG Upgraded: libxcrypt-compat-4.4.34-1.fc38.x86_64 2023-06-07T19:47:34-0700 SUBDEBUG Upgraded: gnome-maps-44.1-1.fc38.x86_64 2023-06-07T19:47:34-0700 SUBDEBUG Upgraded: dbus-1:1.14.6-1.fc38.x86_64 2023-06-07T19:47:34-0700 SUBDEBUG Upgraded: dbus-common-1:1.14.6-1.fc38.noarch 2023-06-07T19:47:34-0700 SUBDEBUG Upgraded: libxcrypt-4.4.34-1.fc38.x86_64 2023-06-07T19:47:34-0700 SUBDEBUG Upgraded: dbus-libs-1:1.14.6-1.fc38.x86_64 2023-06-07T19:47:34-0700 SUBDEBUG Upgraded: ocl-icd-2.3.1-3.fc38.x86_64 2023-06-07T19:47:34-0700 SUBDEBUG Upgraded: ibus-libpinyin-1.15.1-1.fc38.x86_64 2023-06-07T19:47:34-0700 SUBDEBUG Upgraded: epiphany-runtime-1:44.2-1.fc38.x86_64 No, libvirt nor qemu or virsh are not in this list. But so far virsh is the only command affected. Reproducible: Always Steps to Reproduce: 1. virsh * OR virt-viewer * 2. command never returns Actual Results: nothing at all happens.. no journal entries logged. It just hangs. Expected Results: Expect that virsh will return *somemthing*, even if command fails. Actions can be performed with virt-manager, and VMs do run normally.
In the situation when the virsh * commands fail, does it help when you do a `systemctl restart virtnetworkd.service` ?
If yes, you may want to keep an eye on https://bugzilla.redhat.com/show_bug.cgi?id=2213660.
Actually that DID actually unblock the logjam. I'll check out that other bug. I guess this is a duplicate then?
To me it looks like it's duplicate.
Agree. Marking as duplicate. *** This bug has been marked as a duplicate of bug 2213660 ***