Comment 9 for bug 2040189

Tested on jammy using version 23.02-0ubuntu1~22.04.2

a) installed and ran `sudo landscape-config`. Progressed through the wizard until

Request a new registration for this computer now? [y/N]: y
System successfully registered.

ubuntu@driven-mudfish:~$ systemctl is-active landscape-client
active

ubuntu@driven-mudfish:~$ pgrep landscape
2930
2931
2932
2933

ubuntu@driven-mudfish:~$ ps u -p 2930 2931 2932 2933
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 2930 0.0 0.2 50772 37268 ? Ss 21:57 0:00 /usr/bin/python3 /usr/bin/landscape-client
landsca+ 2931 0.0 0.3 286392 49004 ? Sl 21:57 0:00 /usr/bin/python3 /usr/bin/landscape-broker --ignore-sigint
landsca+ 2932 0.0 0.2 146128 45296 ? Sl 21:57 0:00 /usr/bin/python3 /usr/bin/landscape-monitor --ignore-sigint
root 2933 0.0 0.2 60072 41224 ? S 21:57 0:00 /usr/bin/python3 /usr/bin/landscape-manager --ignore-sigint

landscape-client appears to be behaving normally. I dispatched a reboot, a package upgrade, and a package installation.

b) Installed landscape-client 19.12-0ubuntu13
b1) registered via `sudo landscape-config`. Confirmed landscape-client service is running.
Upgraded to landscape-client 23.02-0ubuntu1~22.04.2

The landscape-client service has restarted and is running the latest version. Message exchanges are successful.

Restarting services...
 systemctl restart landscape-client.service

ubuntu@select-emu:~$ tail /var/log/landscape/broker.log
...
2024-03-27 22:15:36,058 INFO [MainThread] Broker stopped with config /etc/landscape/client.conf
2024-03-27 22:15:37,246 INFO [MainThread] Broker started with config /etc/landscape/client.conf
...

b) Installed landscape-client 19.12-0ubuntu13
b2) the landscape-client service is not running
Upgraded to landscape-client 23.02-0ubuntu1~22.04.2

The landscape-client service is still not running:
ubuntu@immune-sheep:~$ systemctl is-active landscape-client
inactive

ubuntu@immune-sheep:~$ ls -l /var/log/landscape/
total 0