Comment 1 for bug 1418139

This has happened twice on the machines we do manual provider testing. This also the same problem with a failed destroy-environment with local-provider. When destroy-environment fails to cleanup resources, a subsequent bootstrap will also fail.

I believe destroy-environment --force does not guarantee cleanup of resources, and several people have used --force in error.

Was this failure seen with a released juju version? Does it happen all the time? What --force used?