Comment 17 for bug 2006402

When I sponsored this for lunar way back, I guess I didn't think about all the consequences of adding --no-stop-on-upgrade to the systemd unit installation, together with the already existing --no-start.

I decided to do a quick test, and registered a jammy lxd container with landscape with the jammy landscape-client (19.12). I then built 23.02 in a ppa, added that to the container, and asked landscape to upgrade landscape-client. The upgrade happened just fine, but the landscape-client processes stayed the same, i.e., no restart:

   3256 ? Ss 0:03 /usr/bin/python3 /usr/bin/landscape-client
   3257 ? Sl 0:03 \_ /usr/bin/python3 /usr/bin/landscape-broker --ignore-sigint
   3258 ? Sl 0:03 \_ /usr/bin/python3 /usr/bin/landscape-monitor --ignore-sigint
   3259 ? S 0:01 \_ /usr/bin/python3 /usr/bin/landscape-manager --ignore-sigint

(before and after)

With 19.12, if there were a point release for it without the systemd change, what exactly would happen? It would upgrade the landscape-client package, but not start the new version, and the machine would remain without a running landscape-client?

And now, I can see it will keep the old landscape-client running, is there a plan to address this? https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/2027613 mentions the rationale, but not how to address restarting landscape-client after a package upgrade.

FWIW, this is the PPA I used to test: https://launchpad.net/~ahasenack/+archive/ubuntu/landscape-client-sru-23.02/