Comment 1 for bug 1406263

At the basis it is not really Heat's problem, as Heat only manages the container itself (we do not have resources for objects inside the containers). If Swift demands a container to be empty on delete so be it. We probably could list all the objects in the container and delete them one by one, but that would be a deviation from Swift behaviour, plus if it was not created by Heat, Heat has no business deleting it.

But surely, the error message can be improved.