Comment 4 for bug 1084273

Sorry for the delay Sam,

So the issue was in my test I was actually creating the volume and setting it's status to 'error' in the db manually. The fact is however if the volume wasn't deployed the api delete call doesn't call the same path (doesn't need to) and and just goes directly to db.volume_destroy which needed admin context.