*** This bug is a duplicate of bug 1484194 ***
https://bugs.launchpad.net/bugs/1484194
** This bug is no longer a duplicate of bug 1476806
Unable to delete instance with attached volumes which failed to boot
** This bug has been marked a duplicate of bug 1484194
Cinder shouldn't fail a detach call for a volume that's not attached
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1480931
Title:
Can't remove error instance which boot from image with new volume
Status in OpenStack Compute (nova):
In Progress
Bug description:
We need to prepare a image which will cause error during build instance.
>> nova image-meta cirros-0.3.4-x86_64-uec set hw_video_ram=5
Nova will raise requested ram too high exception when creating instance.
Then you can get a error instance. But you can't delete it.
You can find there is error message which was raised at
https://github.com/openstack/nova/blob/master/nova/compute/manager.py#L2245
Why this happen?
Nova will detach volume if you create instance failed.
When users try to delete instance, nova will detach again.
And cinder will throw invalid volume at
https://github.com/openstack/cinder/blob/master/cinder/volume/manager.py#L888
Nova don't have try exception block can handle this exception.
Therefore nova can't delete instance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1480931/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
