Comment 8 for bug 1869796

The one thing in the logs (which we have identified before) that is suspicious is:
Apr 01 07:37:26 f2 systemd[1]: libvirtd-ro.socket: Succeeded.
Apr 01 07:37:26 f2 systemd[1]: Closed Libvirt local read-only socket.
Apr 01 07:37:26 f2 systemd[1]: Stopping Libvirt local read-only socket.
Apr 01 07:37:26 f2 systemd[1]: libvirtd-ro.socket: Socket service libvirtd.service already active, refusing.
Apr 01 07:37:26 f2 systemd[1]: Failed to listen on Libvirt local read-only socket.

But it is up and even started at the right time:

root@f2:~# systemctl status libvirtd-ro.socket
● libvirtd-ro.socket - Libvirt local read-only socket
     Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2020-04-01 07:37:26 UTC; 2min 31s ago
   Triggers: ● libvirtd.service
     Listen: /run/libvirt/libvirt-sock-ro (Stream)
     CGroup: /system.slice/libvirtd-ro.socket
Apr 01 07:37:26 f2 systemd[1]: Listening on Libvirt local read-only socket.

It might start it twice and only one fails?
With re-installs on 7:35 and 7:37 the log looks like that:

Mar 31 14:11:06 f2 systemd[1]: Listening on Libvirt local read-only socket.
Apr 01 07:35:19 f2 systemd[1]: Closed Libvirt local read-only socket.
Apr 01 07:35:19 f2 systemd[1]: Stopping Libvirt local read-only socket.
Apr 01 07:35:19 f2 systemd[1]: Failed to listen on Libvirt local read-only socket.
Apr 01 07:35:19 f2 systemd[1]: Listening on Libvirt local read-only socket.
Apr 01 07:37:26 f2 systemd[1]: Closed Libvirt local read-only socket.
Apr 01 07:37:26 f2 systemd[1]: Stopping Libvirt local read-only socket.
Apr 01 07:37:26 f2 systemd[1]: Failed to listen on Libvirt local read-only socket.
Apr 01 07:37:26 f2 systemd[1]: Listening on Libvirt local read-only socket

Each time we see it first fail and then succeed.
I need to check where exactly the two calls come from and if we can remove the former one.