Test builds looked all good, but on the final build one of four tests
failed around:
Setting up libvirt-daemon-system
(7.0.0-2ubuntu2.1~backport20.04-202109210949~ubuntu20.04.1) ...
Job for virtlogd.service failed because the control process exited with error
code.
See "systemctl status virtlogd.service" and "journalctl -xe" for details.
The service actually works fine, and it does restart fine manually as
well as on any subsequent installation/upgrade.
The "problem" a.k.a "feature" is that since it no more re-starts but
only starts the service that might behave oddly at the first transition.
But after the change it should be fine and work better than before (no
one wants logd and lockd to restart in production).
So this is fixed for the initially reported problem and should be fine
overall although the upgrade might cause a small one-off bump.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944413
Title:
upgrading libvirt restarts libvirt-guests.service (when using server-
backports)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1944413/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
