There's no way currently for Cinder to "know" about this situation.
It's actually a failure on Nova's part to clean up after itself when
deleting a VM IMO.
Also.. FYI there's a reset-state extension that you can/should use
rather than manipulating the DB directly.
** Changed in: cinder
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1293631
Title:
when delete a dead VM the status of attached cinder volume is not
updated
Status in Cinder:
Invalid
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
when I terminate a VM which is in suspended status and has a cinder
volume attached, the status of cinder volume can not be updated. the
volume status will be kept as attached and the attached-host in
database isn't updated. the cinder volume becomes an orphan on which
you can't do delete/update/attach/detach. the only option is goto the
database and update the volumes table manually.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1293631/+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
