** Also affects: nova/queens
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => In Progress
** Changed in: nova/pike
Status: New => In Progress
** Changed in: nova/queens
Status: New => In Progress
** Changed in: nova/ocata
Assignee: (unassigned) => Mohammed Naser (mnaser)
** Changed in: nova
Assignee: Ankit Agrawal (ankitagrawal) => melanie witt (melwitt)
** Changed in: nova/pike
Assignee: (unassigned) => Mohammed Naser (mnaser)
** Changed in: nova/queens
Assignee: (unassigned) => Mohammed Naser (mnaser)
** Changed in: nova/ocata
Importance: Undecided => Medium
** Changed in: nova
Importance: Low => Medium
** Changed in: nova/pike
Importance: Undecided => Medium
** Changed in: nova/queens
Importance: Undecided => Medium
--
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) ocata series:
In Progress
Status in OpenStack Compute (nova) pike series:
In Progress
Status in OpenStack Compute (nova) queens series:
In Progress
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
