instance state polling finds compute instance not in DB
Bug #754051 reported by
Trey Morris
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Josh Kearney |
Bug Description
using xenserver - this is found in the compute log:
2011-04-07 20:50:07,213 WARNING nova.compute.
probably want the domU to be ignored entirely. It will need to be handled separately from other orphaned VMs eventually anyway.
Related branches
lp:~jk0/nova/lp754051
- Rick Harris (community): Approve
- Devin Carlen (community): Approve
-
Diff: 16 lines (+6/-3)1 file modifiednova/compute/manager.py (+6/-3)
Changed in nova: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in nova: | |
status: | Confirmed → In Progress |
assignee: | nobody → Josh Kearney (jk0) |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → diablo-1 |
Changed in nova: | |
milestone: | diablo-1 → 2011.3 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Oooh... nice bug. I suggest that the best fix would be that the XenServer driver shouldn't return the host machine, rather than handling this in the polling layer. I think that's what you're suggesting anyway!