Instance not found bug when delete instance without nova-compute service
Bug #1087588 reported by
Peng YuWei
This bug report is a duplicate of:
Bug #1067214: forget to release resource when terminate an instance from a failed compute node.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
If you delete a instance when nova-compute service not running, call
nova floating-ip-list
will raise
InstanceNotFound: Instance 7157e105-
bug in nova-API. And floating-ip-list got nothing but a error.
Look the code in
nova/api/
we can see if call floating-list, it will get instance_uuid first.
If instance_uuid not exist in table instances, it will raise a exception.
query nova database, I see the instance_uuid not remove in table 'fixed_ips'
Revision history for this message
| Chuck Short (zulcss) wrote | #1 |
| Changed in nova: | |
| status: | New → Incomplete |
Revision history for this message
| Peng YuWei (pengyuwei) wrote | #2 |
| Changed in nova: | |
| status: | Incomplete → Triaged |
| importance: | Undecided → Critical |
Revision history for this message
| Dan Smith (danms) wrote | #3 |
Revision history for this message
| Dan Smith (danms) wrote | #4 |
Revision history for this message
| Dan Smith (danms) wrote | #5 |
| Changed in nova: | |
| milestone: | none → 2012.2.2 |
| status: | Triaged → Fix Released |
Revision history for this message
| Thierry Carrez (ttx) wrote | #6 |
| Changed in nova: | |
| milestone: | 2012.2.2 → grizzly-2 |
| milestone: | grizzly-2 → none |
To post a comment you must log in.
Which version is this with?