Comment 2 for bug 1622813

I'm not entirely sure if it's the provisioner's fault yet.

I tested it a little differently, by using "add-machine -n 10" and then destroying the model. That time, all of the machines were stopped in one go.

I then did what I originally did, and deployed a bundle. This time, canonical-kubernetes. The units/applications get torn down gracefully, so not *all* the machines are in the "dead" state by the time the provisioner finds the first one is. That's fine. But once it's done stopping that instance, they are all in the dead state... and it's still stopping them one at a time.