Comment 2 for bug 1988312

The Anbox Cloud CI is running into this currently and it's causing our tests to fail as we wait for the Juju model to converge to active by using juju-wait (which waits for all workload status to switch to active).

Reproducing is rather simple here:

$ juju add-model lp1988312
$ juju deploy ubuntu
$ juju deploy telegraf
$ juju relate ubuntu telegraf

Once everything has settled

Model Controller Cloud/Region Version SLA Timestamp
lp1988312 dev-controller localhost/localhost 2.9.33 unsupported 16:12:22+02:00

App Version Status Scale Charm Channel Rev Exposed Message
telegraf maintenance 1 telegraf stable 57 no Installing python3-netifaces,python3-yaml,sysstat,telegraf
ubuntu 20.04 active 1 ubuntu stable 20 no

Unit Workload Agent Machine Public address Ports Message
ubuntu/0* active idle 0 10.25.83.190
  telegraf/0* maintenance idle 10.25.83.190 Installing python3-netifaces,python3-yaml,sysstat,telegraf

Machine State Address Inst id Series AZ Message
0 started 10.25.83.190 juju-8977bc-0 focal Running

We're going to ignore the telegraf units for now when calling juju-wait