Comment 7 for bug 907808

I agree with removing the decorator on delete for now.... and dealing with the consequences. I don't think it's a problem for 'BUILD'. We'll get exceptions, as you mention, but they wouldn't cause any harm. I think for resize we may just need to deal with it until we can come up with something better.

And yeah, it is definitely an issue that 'task_state' is not exposed to a user, but we have restrictions on it and return 409s when vm_state is ACTIVE. From the API docs, it'll say ACTIVE is a valid state for the action.. yet we might 409 because task_state is 'snapshotting'. User has no idea what's going on, although the message being returned is somewhat informative.

#3 would be helpful... With #1, allow delete... but move the instance if it's in BUILD state and it is of a certain age.