I've seen some issues having it kill machines. To work around it you can manually remove them: juju remove-machine 1 2 3
That gets them dying and removed and then the model can die. John =:-> On Dec 23, 2016 12:54 AM, "Daniel Bidwell" <drbidw...@gmail.com> wrote: I am running juju version 2.0.2 with maas 2.1 and am trying to destory my environment so I can start over again with it. juju status looks like: $ juju status Model Controller Cloud/Region Version default maasmaster-controller maasmaster 2.0.1 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 10.20.9.129 4y3h7q xenial acauits 1 started 10.20.9.130 4y3h7r xenial acauits 2 stopped 10.20.9.131 4y3h7s xenial acauits 3 started 10.20.9.132 xsngbs xenial acauits There are no apps running. All of the machines are removed and ready for redeployment. juju destroy-model default just keeps spinning with: Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... Waiting on model to be removed, 4 machine(s)... How do I kill this sucker so I can move on? -- Daniel Bidwell <drbidw...@gmail.com> -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/ mailman/listinfo/juju-dev
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
