Comment 6 for bug 1869796

Thanks Seth,
then there isn't much more left than retrying this a few times on focal and see if I can reproduce.
Otherwise it will be incomplete until we have a better view on this :-/

Since we didn't change anything on the services in the last upload we can use the following for the same upgrade path:
  $ apt install --reinstall libvirt-daemon-system

And indeed with that I was able to recreate it:
root@f2:~# apt install --reinstall libvirt-daemon-system
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded.
Need to get 67.5 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu focal/main amd64 libvirt-daemon-system amd64 6.0.0-0ubuntu6 [67.5 kB]
Fetched 67.5 kB in 0s (440 kB/s)
Preconfiguring packages ...
(Reading database ... 46975 files and directories currently installed.)
Preparing to unpack .../libvirt-daemon-system_6.0.0-0ubuntu6_amd64.deb ...
Unpacking libvirt-daemon-system (6.0.0-0ubuntu6) over (6.0.0-0ubuntu6) ...
Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
Job failed. See "journalctl -xe" for details.
virtlockd.service is a disabled or a static unit, not starting it.
virtlogd.service is a disabled or a static unit, not starting it.
Setting up libvirt-daemon dnsmasq configuration.
root@f2:~# echo $?
0

So no bad RC, just warning - but which and why exactly is the question.