systemd: do not restart sockets
Sockets need to be started on install to be ready (drop --no-start), but not
stopped/restarted (add --no-stop-on-upgrade, drop --no-restart-after-upgrade)
later on to prevent issues on upgrade (on running services) or reinstall
(breaking the .sockets state)
Details:
- drop --no-start:
.socket removed without being stopped will enter a faulty state that can only
be recovered with a restart of the socket. We restart the service (libvirtd)
backing the sockets anyway, the sockets can and should stay up as-is.
- drop --no-restart-after-upgrade:
`--no-restart-after-upgrade` does not prevent restarts. It only controls
when the restart happens, but we want no restart at-all so drop it.
- add --no-stop-on-upgrade:
This needs to be added to not touch the .sockets state at all on
upgrades.
LIBVIRT_NOSTART_UNITS nowadays only includes SOCKETS and their handling is
rather special, so this changes the name to LIBVIRT_SOCKETS to be more obvious
when touching d/rules
Signed-off-by:
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Loading
-
mentioned in merge request !132 (closed)
-
mentioned in merge request !163 (merged)
Please register or sign in to comment