Comment 2 for bug 1784730

Not sure if it is related to this bug, but another issue that I am facing on this same deploy is that some of the containers are accusing as already existing.
This is a fresh deploy, from a couple of weeks ago. I have only one controller, which configures everything.

Machine State DNS Inst id Series AZ Message
4 started 10.5.0.8 85489d7b-a094-40b3-9083-430940037081 bionic nova ACTIVE
4/lxd/0 started 10.143.150.26 juju-5ed1b3-4-lxd-0 bionic nova Container started
4/lxd/1 pending juju-5ed1b3-4-lxd-1 bionic nova Container started
4/lxd/2 pending juju-5ed1b3-4-lxd-2 bionic nova Container started
5 started 10.5.0.15 821a9119-30b3-4f85-8b94-12e0896b72a3 bionic nova ACTIVE
5/lxd/0 pending juju-5ed1b3-5-lxd-0 bionic nova Container started
5/lxd/1 down pending bionic Container 'juju-5ed1b3-5-lxd-1' already exists
5/lxd/2 pending juju-5ed1b3-5-lxd-2 bionic nova Container started
6 started 10.5.0.7 8202c07f-23f8-4ee9-a6aa-1951635254a3 bionic nova ACTIVE
6/lxd/0 down pending bionic Container 'juju-5ed1b3-6-lxd-0' already exists
6/lxd/1 pending juju-5ed1b3-6-lxd-1 bionic nova Container started
6/lxd/2 pending juju-5ed1b3-6-lxd-2 bionic nova Container started
7 started 10.5.0.10 42a3a3c7-b982-41aa-962e-ad46bcb5b7a8 bionic nova ACTIVE
7/lxd/0 pending juju-5ed1b3-7-lxd-0 bionic nova Container started
7/lxd/1 pending juju-5ed1b3-7-lxd-1 bionic nova Container started
7/lxd/2 pending juju-5ed1b3-7-lxd-2 bionic nova Container started