Discussion with Debian systemd folks went great. It seems mid/long term we will get dh_installsystemd to do the right thing.
For now (Freeze ahead) we want something for Ubuntu to make it actually work now as it is super-unlikely to get the dh_ changes and pick them up in time for this Compar 8 package as it is now. The solution for us might be to drop both sysV scripts (as tried before) but also drop the "Also=" lines from the install section of libvirtd.service. That should stop the tools from doing the wrong thing and was also found to potentially actively harm e.g. enable/disable will do so for all sockets as well. The service already has a requires dependency to the sockets, so we should loose nothing. I have built and tested this from a PPA. It works as it should now. - the new virtlogd-admin.socket is installed and enabled, but off (can't start due to service running already) - after a reboot or full service restart that is all fine - the virtlogd service is staying up through the upgrades - libvirtd itself is restarted as it should (after upgrade) - the upgrade works with info messages, but not failing the upgrade I'll suggest that to Debian, but they might wait for the fix in the dh_*systemd* tools. We will probably have to take the solution as outlined to be in the Feature Freeze. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786179 Title: double virtlogd sockets with services running can trigger issues on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786179/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
