Comment 2 for bug 2019086

I'm also seeing this in a deployment.

In my case, all three units (including the leader) are waiting for db.

Also, removing and re-adding relation does not help, in fact make it worse, the three units become blocked with message:

ubuntu@infra01:~$ juju status landscape-server landscape-postgresql
Model Controller Cloud/Region Version SLA Timestamp
lma-maas foundations-maas maas_cloud 2.9.44 unsupported 20:24:07Z

App Version Status Scale Charm Channel Rev Exposed Message
landscape-postgresql 12.16 active 2 postgresql latest/stable 316 no Live master (12.16)
landscape-server blocked 3 landscape-server stable 87 no Failed to update database schema

Unit Workload Agent Machine Public address Ports Message
landscape-postgresql/0* active idle 4 10.3.4.130 5432/tcp Live master (12.16)
landscape-postgresql/1 active idle 10 10.3.4.117 5432/tcp Live secondary (12.16)
landscape-server/0* blocked idle 3 10.3.4.132 Failed to update database schema
landscape-server/1 blocked idle 9 10.3.4.129 Failed to update database schema
landscape-server/2 blocked idle 16 10.3.4.119 Failed to update database schema

Machine State Address Inst id Series AZ Message
3 started 10.3.4.132 landscape-1 focal zone1 Deployed
4 started 10.3.4.130 landscapesql-1 focal zone1 Deployed
9 started 10.3.4.129 landscape-2 focal zone3 Deployed
10 started 10.3.4.117 landscapesql-2 focal zone3 Deployed
16 started 10.3.4.119 landscape-3 focal zone5 Deployed