scheduler api's reroute_compute should better handle cases where a child zone is dead
Bug #844165 reported by
Chris Behrens
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Chris Behrens |
Bug Description
Set up a top level zone with an API/scheduler. Create 2 child zones... but only start up one of them. Build an instance. When you do a 'show uuid' to the top level API, an exception will be returned because it can't query all child zones (1 is dead) even though the zone that has the UUID is alive and well.
Related branches
lp:~cbehrens/nova/lp844165
- Josh Kearney (community): Approve
- Sandy Walsh (community): Approve
-
Diff: 251 lines (+139/-22)3 files modifiednova/exception.py (+7/-0)
nova/scheduler/api.py (+35/-17)
nova/tests/scheduler/test_scheduler.py (+97/-5)
Changed in nova: | |
status: | New → In Progress |
assignee: | nobody → Chris Behrens (cbehrens) |
summary: |
- abstract scheduler's reroute_compute should better handle cases where a - child zone is dead + scheduler api's reroute_compute should better handle cases where a child + zone is dead |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → diablo-rbp |
Changed in nova: | |
milestone: | diablo-rbp → 2011.3 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.