destroy-all-controllers doesn't release maas machines

[Andrew McLeod]

juju version 2.5.3-bionic-amd64

MAAS version: 2.3.5 (6511-gf466fdb-0ubuntu1~16.04.1)

Problem: when using destroy-controllers --destroy-all-models, the model is removed before the machines are removed - meaning that they are still marked as Deployed in MAAS

Expected: machines removed (released) from maas before model is removed

Some logs:

jenkins@mosci-ppc64el-jslave-persist-95:~$ juju controllers
jUse --refresh option with this command to see the latest information.

Controller Model User Access Cloud/Region Models Machines HA Version
ppc64el-mosci-ruxton-maas* ppc64el-mosci-ruxton-maas admin superuser ruxton-maas 3 1 none 2.5.3

jenkins@mosci-ppc64el-jslave-persist-95:~$ juju destroy-controller ppc64el-mosci-ruxton-maas --destroy-all-models
WARNING! This command will destroy the "ppc64el-mosci-ruxton-maas" controller.
This includes all machines, applications, data and other resources.

Continue? (y/N):y
Destroying controller
Waiting for hosted model resources to be reclaimed
Waiting on 2 models, 16 machines, 16 applications
Unable to get the controller summary from the API: model b2243a4e-e738-454b-8d33-ae5aaac03959 has been removed.
All hosted models reclaimed, cleaning up controller machines

jenkins@mosci-ppc64el-jslave-persist-95:~$ juju controllers
ERROR No controllers registered.

Please either create a new controller using "juju bootstrap" or connect to
another controller that you have been given access to using "juju register".

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.