Comment 3 for bug 1677240

Juju doesn't provide any command to destroy or delete the storage that was created during charm/unit creation or any added storage using juju 'add-storage' command. Juju deletes storage automatically that were bounded to the charm/unit on running 'remove-unit' or 'remove-application' or 'remove-machine'.

Now a couple of questions to go further on this issue.

Do you see any instance in AWS other than storage volumes? I am asking this because EBS volumes which do not have "Delete on Termination" set to true will persist after this instance is terminated.
I don't think that juju deploy changed any property on this in recent time.

>> After deleting the "available" volumes, tests started to pass again.
Why "EBS volume time out" error stops any further instance to launch on the AWS region?
I don't think AWS has a limit on EBS volumes per region.

>> I suspect the issue assess_storage.py test should be deleting the volumes when it is done
Juju doesn't provide any command to remove/delete or destroy the storage volumes that were added using "add-storage" or "create-storage-pool";

All resources that were allocated will be released on destroying the controller or immediately after coming out from the bootstrap context manager. A quick look into assess_storage.py doesn't show any leak on this properties.

>> This is a spike starting with build revision 5063 starting on March 28
How can I get the changes that went on each revision? Please let me know the link to see them and I hope it will also show me the code changes too.