There are two sections in the postinst both added by
dh_installsystemd/12.9ubuntu1
1. restart on upgrade, start otherwise
if [ -n "$2" ]; then
_dh_action=restart
else
_dh_action=start
fi
deb-systemd-invoke $_dh_action 'libvirtd-ro.socket' 'libvirtd.service'
'libvirtd.socket' 'virtlockd.socket' 'virtlogd.socket' >/dev/null || true
2. unconditional start
deb-systemd-invoke start 'libvirt-guests.service' 'libvirtd-admin.socket'
'libvirtd-ro.socket' 'libvirtd.socket' 'virtlockd-admin.socket'
'virtlockd.service' 'virtlockd.socket' 'virtlogd-admin.socket'
'virtlogd.service' 'virtlogd.socket' >/dev/null || true
We have two calls to dh_installsystemd indeed in r/rules:
255 »···dh_installsystemd -p libvirt-daemon-system --restart-after-upgrade
libvirtd.service
256 »···dh_installsystemd -p libvirt-daemon-system --no-stop-on-upgrade
--no-restart-after-upgrade $(LIBVIRT_SYSTEM_SERVICES)
Of these line 256 is all the auxiliary services with no-stop.
It matches the unconditional start we see in #2 due to "--no-stop-on-upgrade
--no-restart-after-upgrade"
On line 255 we have the actual service restart.
It seems that the rule for libvirtd.service is pulling in a bunch of .socket
files without us calling for it (maybe all dependent ones). Yep it matches:
root@f2:~# grep Also /lib/systemd/system/libvirtd.service
Also=virtlockd.socket
Also=virtlogd.socket
Also=libvirtd.socket
Also=libvirtd-ro.socket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869796
Title:
vague error during upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1869796/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
