Comment 5 for bug 1514437

I got a hold of Sridhar on this. The short answer is that I think this defect can be canceled.

What happened:
 - User started the destroy operation for a VM.
 - User immediately kicked off a detach_interface operation while the destroy was still ongoing

Had the destroy finished before the detach_interface was called, a 404 (instance not found) error would have been exposed. However, the instance did still exist when the command came in.

That led to the issue. I think that this is more a usability issue. It is perfectly OK for the compute log to provide messaging around this.