If no hosts found during resize, scheduler will leave instance stuck in RESIZE
Bug #928521 reported by
Johannes Erdfelt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Andrew Clay Shafer |
Bug Description
While doing a resize to a very large instance type, the scheduler was left with no hosts to schedule to:
2012-02-07 21:55:33,247 WARNING nova.scheduler.
Unfortunately, this left the instance stuck in RESIZE.
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → essex-4 |
Changed in nova: | |
assignee: | nobody → Andrew Clay Shafer (littleidea) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
This and a few other states are interesting cos they are in a fungible state, it's not an error state, but still a user request could not be completed. So would this just be marked as ERROR even if the instance is alive, and let the user know with an asynchronous fault that the instance could not be resized?
I'm not sure how such states are currently being handled in nova.