can't delete a error instance(boot from volume )

[Rongze Zhu]

The Reproduce steps:

I create a volume from image(the cinder backend is HDS FC Storage).

Then I boot a instance from the volume, the call path is "nova-api => nova-compute => cinder-api => cinder-volume".
Because the HDS Driver in cinder-volume is slow in my env, so nova-compute will timeout and set the status of instance as "error".

Then I try to delete the instance, because the value of 'os-extended-volumes:volumes_attached' in the instance is the volume id, so nova-compute will call detach-volume API in cinder-api. Because the status of volume in cinder database is 'available', so the cinder-api will raise a 'VolumeAttachmentNotFound' exception. Finally, I failed to delete the error instance.

Solution：

nova-compute need to check the status of volume before call detach-volume api to cinder-api.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/287253

[OpenStack Infra (hudson-openstack)]

Change abandoned by Michael Still (<email address hidden>) on branch: master
Review: https://review.openstack.org/287253
Reason: This patch is quite old, so I am abandoning it to keep the review queue manageable. Feel free to restore the change if you're still interested in working on it.

[Sean Dague (sdague)]

There are no currently open reviews on this bug, changing
the status back to the previous state and unassigning. If
there are active reviews related to this bug, please include
links in comments.

[Sean Dague (sdague)]

This change was abandoned over a year ago, can we get confirmation that it's still an issue?

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]