Comment 9 for bug 1967177

we've been flagging test runs in the SQA lab with this bug lately as we've seen a large number of cases where all but one unit in a service is up and running, and the one unit that isn't running says its missing a relation.

Most often these services are mysql-router's which are not getting the shared-db relation to finish or trigger a hook.

Here are some logs from a recent example, where neutron-api-mysql-router/0 (the leader unit) is waiting on "'shared-db' incomplete, Waiting for proxied DB creation from cluster" for a little over 3 hours.

We've recently added more logs to the juju-crashdump as well. Each units folder now has logs for juju show-machine and juju show-unit as well as the juju show-status-log.

Crashdump: https://oil-jenkins.canonical.com/artifacts/6834065e-9050-48a1-9da2-660752d77bba/generated/generated/openstack/juju-crashdump-openstack-2022-05-03-15.01.53.tar.gz

Controller Crashdump:https://oil-jenkins.canonical.com/artifacts/6834065e-9050-48a1-9da2-660752d77bba/generated/generated/juju_maas_controller/juju-crashdump-controller-2022-05-03-15.12.42.tar.gz

Testrun:https://solutions.qa.canonical.com/testruns/testRun/6834065e-9050-48a1-9da2-660752d77bba
All the logs for the run can be found at the "view artifacts for this run" at the bottom of the page.