Comment 8 for bug 1245775

I think safe_delete_from_backend is meant to catch all the exceptions and not raise them. I think that is what 'safe' means in this context, it's kind of like a best effort cleanup if something else went wrong.

Is the real bug here that delete in the Controller should not be calling 'safe_delete_from_backend' and instead needs to call a delete that could raise a 404? What exact case does this matter? An image may not have data in the store but still have an image entity that is deleted in glance. Just trying to understand :)