Bug 2213584

Summary: All virsh commands hang, but using virt-manager is OK
Product: [Fedora] Fedora Reporter: Bill Taroli <bill.taroli>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 38CC: berrange, cagney, clalancette, crobinso, jforbes, laine, libvirt-maint, Michael.Riss, virt-maint
Target Milestone: ---Keywords: Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://bugzilla.redhat.com/show_bug.cgi?id=1882093
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-12 18:20:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Bill Taroli 2023-06-08 15:56:04 UTC 
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.
Comment 1 Michael Riss 2023-06-08 21:37:56 UTC 
In the situation when the virsh * commands fail, does it help when you do a `systemctl restart virtnetworkd.service` ?
Comment 2 Michael Riss 2023-06-08 22:21:02 UTC 
If yes, you may want to keep an eye on https://bugzilla.redhat.com/show_bug.cgi?id=2213660.
Comment 3 Bill Taroli 2023-06-12 15:29:29 UTC 
Actually that DID actually unblock the logjam. I'll check out that other bug. I guess this is a duplicate then?
Comment 4 Michael Riss 2023-06-12 18:06:54 UTC 
To me it looks like it's duplicate.
Comment 5 Bill Taroli 2023-06-12 18:20:17 UTC 
Agree. Marking as duplicate.

*** This bug has been marked as a duplicate of bug 2213660 ***