Comment 0 for bug 2022982

If somebody follows the Juju installation instructions as seen on: https://ubuntu.com/landscape/install

Within 2 weeks the Landscape Server unit looks like this:

ubuntu@landscape-beta:~$ juju status
Model Controller Cloud/Region Version SLA Timestamp
landscape-model landscape-controller localhost/localhost 3.1.2 unsupported 23:23:45Z

App Version Status Scale Charm Channel Rev Exposed Message
haproxy active 1 haproxy stable 66 yes Unit is ready
landscape-server active 0/1 landscape-server stable 79 no Unit is ready
postgresql 12.15 active 1 postgresql latest/stable 270 no Live master (12.15)
rabbitmq-server 3.8.2 active 1 rabbitmq-server stable 123 no Unit is ready

Unit Workload Agent Machine Public address Ports Message
haproxy/0* active idle 0 10.251.146.186 80,443/tcp Unit is ready
landscape-server/0 unknown lost 1 10.251.146.75 agent lost, see 'juju show-status-log landscape-server/0'
postgresql/0* active idle 2 10.251.146.217 5432/tcp Live master (12.15)
rabbitmq-server/0* active idle 3 10.251.146.94 5672/tcp Unit is ready

Machine State Address Inst id Base AZ Message
0 started 10.251.146.186 juju-acf4dc-0 ubuntu@20.04 Running
1 down 10.251.146.75 juju-acf4dc-1 ubuntu@22.04 Running
2 started 10.251.146.217 juju-acf4dc-2 ubuntu@20.04 Running
3 started 10.251.146.94 juju-acf4dc-3 ubuntu@20.04 Running
ubuntu@landscape-beta:~$ juju --version
3.2.0-genericlinux-arm64
ubuntu@landscape-beta:~$ lxc --version
5.14

This happens on Landscape Beta and Landscape Stable.