Can't force delete an errored instance with no info cache
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Vladik Romanovsky | ||
Icehouse |
Fix Released
|
Medium
|
Abhishek Kekane |
Bug Description
Sometimes when an instance fails to launch for some reason when trying to delete it using nova delete or nova force-delete it doesn't work and gives the following error:
This is when using cells but I think it possibly isn't cells related. Deleting is expecting an info cache no matter what. Ideally force delete should ignore all errors and delete the instance.
2014-05-06 10:48:58.368 21210 ERROR nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
2014-05-06 10:48:58.368 21210 TRACE nova.cells.
tags: | added: compute |
Changed in nova: | |
assignee: | nobody → Vladik Romanovsky (vladik-romanovsky) |
Changed in nova: | |
importance: | Undecided → Medium |
tags: | added: icehouse-backport-potential |
Changed in nova: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | juno-3 → 2014.2 |
I'm wondering why the info_cache does not exist for that instance.