We get scheduler json configuration too fast
Bug #1625882 reported by
huangtianhua
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
huangtianhua | ||
Newton |
Fix Committed
|
Medium
|
huangtianhua |
Bug Description
Now we allow to get scheduler configuration too fast, due we don't set the flag 'last_checked' after we checked, the value of flag 'last_checked' is always None,
but the original logic is that we don't have to check the changes of scheduler configuration within 5 minutes again.
Changed in nova: | |
assignee: | nobody → huangtianhua (huangtianhua) |
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
status: | Incomplete → In Progress |
Changed in nova: | |
assignee: | huangtianhua (huangtianhua) → Ed Leafe (ed-leafe) |
Changed in nova: | |
assignee: | Ed Leafe (ed-leafe) → John Garbutt (johngarbutt) |
Changed in nova: | |
importance: | Undecided → Medium |
assignee: | John Garbutt (johngarbutt) → huangtianhua (huangtianhua) |
description: | updated |
To post a comment you must log in.
Not sure I understand the problem ? Could you please explain what's wrong with the scheduler ?