Bug 1212396

Note that this could be linked to https://bugzilla.suse.com/show_bug.cgi?id=1212195, however Comment 9 therein (https://bugzilla.suse.com/show_bug.cgi?id=1212195#c9) makes me believe that this is a different issue, as I'm still using the monolithic daemon.

(In reply to Felix Niederwanger from comment #0)
> Created attachment 867589 [details]
> journal
> 
> Sind updating to TW snapshot 20230612 (+/- 2), listing of virtual machines
> via `virsh list` or virt-manager appears frozen.
> 
> > virsh list
> > # never list anything, even after waiting for 5+ minutes.
> 
> After encountering the issue the first time I reconfigured my system
> according to
> https://doc.opensuse.org/documentation/leap/virtualization/html/book-
> virtualization/cha-libvirt-overview.html, i.e.:
> 
> > systemctl enable libvirtd.socket
> > systemctl enable libvirtd-ro.socket
> > systemctl enable libvirtd-admin.socket
> > systemctl disable libvirtd-tcp.socket
> > systemctl disable libvirtd-tlt.socket
> > systemctl disable libvirtd-tls.socket
> 
> ## Workaround
> 
> Restarting the libvirtd.service resolves the issue temporarily, however
> after some time, `virsh list` and virt-manager are again choking on
> "Connecting ..."

This behavior sounds like https://github.com/systemd/systemd/issues/27953. I just updated one of my TW machines and it now has systemd 253.5. Maybe I'll see the issue too. There's a patch for systemd in this PR https://github.com/systemd/systemd/pull/28035

(In reply to James Fehlig from comment #2)
> ...
> This behavior sounds like https://github.com/systemd/systemd/issues/27953. I
> just updated one of my TW machines and it now has systemd 253.5. Maybe I'll
> see the issue too. There's a patch for systemd in this PR
> https://github.com/systemd/systemd/pull/28035

https://github.com/systemd/systemd/issues/27953 is now fixed upstream via https://github.com/systemd/systemd/pull/28000 which reverted the buggy commit that seems to have been the root cause of the regression.

i'm unfamiliar with the factory build and release process. what's the process of requesting that this fix from upstream be incorporated?

(In reply to dev from comment #3)
> (In reply to James Fehlig from comment #2)
> > ...
> > This behavior sounds like https://github.com/systemd/systemd/issues/27953. I
> > just updated one of my TW machines and it now has systemd 253.5. Maybe I'll
> > see the issue too. There's a patch for systemd in this PR
> > https://github.com/systemd/systemd/pull/28035
> 
> https://github.com/systemd/systemd/issues/27953 is now fixed upstream via
> https://github.com/systemd/systemd/pull/28000 which reverted the buggy
> commit that seems to have been the root cause of the regression.
> 
> i'm unfamiliar with the factory build and release process. what's the
> process of requesting that this fix from upstream be incorporated?

We can ask the systemd-maintainers to add the patch to the Factory package.

The fix/revert has just been submitted to Factory: https://build.opensuse.org/request/show/1094372

(In reply to Franck Bui from comment #5)
> The fix/revert has just been submitted to Factory:
> https://build.opensuse.org/request/show/1094372

Thanks! This fixed the issue for me. I'll let Felix give it a try and ensure it fixes the issue in his environment before closing.

*** Bug 1212480 has been marked as a duplicate of this bug. ***

Hey James,

sorry, I was on a trail in Norway last week with no laptop and internet :-)

After installing TW snapshot 20230624 the issue appears as resolved on my laptop. I think we can close this as resolved.

(In reply to Felix Niederwanger from comment #8)
> Hey James,
> 
> sorry, I was on a trail in Norway last week with no laptop and internet :-)

Nice!

> After installing TW snapshot 20230624 the issue appears as resolved on my
> laptop. I think we can close this as resolved.

Yes, snapshot 20230624 contains the systemd request referenced in #5. I think we can close this bug now and handle any residual libvirt modular daemon issues (like adding the various sockets to openSUSE presets) in bug#1212195.

Thanks for the fix!