destroy-controller doesn't shut down containers (on controller machine)

[John A Meinel]

I was trying to destroy an old juju controller I had running on MAAS, and had something like:

  juju bootstrap maas21
  juju add-machine lxd:0
  juju add-machine lxd:0

  juju destroy-controller --destroy-all-models maas21

And it got stuck in:
Waiting on 0 model, 3 machines

Doing status showed:
$ juju status -m maas21:controller
Model Controller Cloud/Region Version
controller maas21 maas21 2.2-alpha2.3

App Version Status Scale Charm Store Rev OS Notes

Unit Workload Agent Machine Public address Ports Message

Machine State DNS Inst id Series AZ
0 started 172.16.101.29 q8rc6k xenial default
0/lxd/4 started 172.16.102.34 juju-fb41b3-0-lxd-4 xenial
0/lxd/5 started 172.16.102.36 juju-fb41b3-0-lxd-5 xenial
0/lxd/6 started 172.16.102.40 juju-fb41b3-0-lxd-6 xenial

Which shows that they weren't flagged to be stopped. I could stop them normally with:

juju remove-machine --force 0/lxd/4 0/lxd/5 0/lxd/6

(I don't know if --force was required, I didn't try it without)

After which:
  juju destroy-controller --destroy-all-models maas21
succeeded very quickly.

This may be because they were containers on machine 0, vs some other machine where we would be trying to kill the host machine first?

[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.