Zone Manager does not "expire" offline hosts
Bug #800759 reported by
Ed Leafe
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
USC-ISI | ||
Bug Description
The current Zone Manager holds a dict of services and host capabilities, and adds/updates information as the services report their status periodically. However, if a host is running and then goes offline, the Zone Manager dict still includes that host as if it were active.
The code to expire hosts that are no longer available was written in a separate branch but never included in any of the piecemeal dist-scheduler merges. It can be found here:
Related branches
lp:~usc-isi/nova/bug-fix-800759
- Josh Kearney (community): Approve
- Brian Waldon (community): Approve
- Mark Washenberger (community): Needs Information
-
Diff: 262 lines (+209/-0)3 files modifiedAuthors (+2/-0)
nova/scheduler/zone_manager.py (+32/-0)
nova/tests/test_zones.py (+175/-0)
| Changed in nova: | |
| assignee: | nobody → Sandy Walsh (sandy-walsh) |
| status: | New → Confirmed |
| Changed in nova: | |
| importance: | Undecided → Medium |
| status: | Confirmed → Triaged |
| Changed in nova: | |
| assignee: | Sandy Walsh (sandy-walsh) → USC-ISI (usc-isi) |
| status: | Triaged → In Progress |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → diablo-3 |
| Changed in nova: | |
| milestone: | diablo-3 → 2011.3 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
