** Also affects: nova/queens
Importance: Undecided
Status: New
** Tags added: queens-rc-potential volumes
** Also affects: nova/pike
Importance: Undecided
Status: New
--
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/1750666
Title:
Deleting an instance before scheduling with BFV fails to detach volume
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) pike series:
New
Status in OpenStack Compute (nova) queens series:
New
Bug description:
If you try to boot and instance and delete it early before scheduling,
the '_delete_while_booting' codepath hits
`_attempt_delete_of_buildrequest` which tries to remove the block
device mappings.
However, if the cloud contains compute nodes before Pike, no block
device mappings will be present in the database (because they are only
saved if using the new attachment flow), which means the attachment
IDs are empty and the volume delete fails:
2018-02-20 16:02:25,063 WARNING [nova.compute.api] Ignoring volume
cleanup failure due to Object action obj_load_attr failed because:
attribute attachment_id not lazy-loadable
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1750666/+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
