** No longer affects: nova/ocata -- 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/1408527
Title: Delete instance without block_device_mapping record in database after schedule error Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) pike series: Fix Committed Status in OpenStack Compute (nova) queens series: Fix Committed Bug description: When a instance with cinder volume is failed to be scheduled to a host, its status becomes error. Now I delete it successfully, but in block_device_mapping table of nova database, the volume information of the instance is still kept, and not deleted. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1408527/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
