Old scheduler fanout queues are left behind after scheduler restart
Bug #803165 reported by
Antony Messerli
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Chris Behrens |
Bug Description
Scheduler fanout queues are left behind after restarting the service. They also continue to receive messages in them but they never are cleared out since there is no consumer. scheduler_
scheduler_
scheduler 0
scheduler.z1-api1 0
scheduler_
scheduler_
scheduler_
Running rev 1215.
Related branches
lp:~cbehrens/nova/lp803165
- Josh Kearney (community): Approve
- Brian Lamar (community): Needs Information
- Matt Dietz (community): Approve
- Ed Leafe (community): Approve
-
Diff: 15 lines (+5/-0)1 file modifiednova/rpc.py (+5/-0)
Changed in nova: | |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
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.
We're missing auto_delete=True on fanout queues... OR... maybe the scheduler fanout queue should use scheduler_ fanout_ hostname vs scheduler_ fanout_ UUID.