Addition/Removal of a baremetal node does not propagate to scheduler quickly
Bug #1260102 reported by
aeva black
This bug report is a duplicate of:
Bug #1248022: Nova scheduler not updated immediately when a baremetal node is added or removed.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Triaged
|
Wishlist
|
Unassigned | ||
| OpenStack Compute (nova) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
With the baremetal driver, if a baremetal node is added/deleted, it is not removed from pool of available resources until the next run of update_
This bug will also apply to the ironic driver, which will rely on the same mechanism(s) for listing and scheduling compute resources.
| Changed in nova: | |
| status: | New → Triaged |
| tags: | added: baremetal scheduler |
| tags: | added: ironic |
| Changed in nova: | |
| importance: | Undecided → Medium |
| summary: |
- Removal of a baremetal node does not propagate to scheduler quickly + Addition/Removal of a baremetal node does not propagate to scheduler + quickly |
| description: | updated |
Revision history for this message
| aeva black (tenbrae) wrote | #1 |
| Changed in ironic: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| importance: | Medium → Wishlist |
| tags: |
added: nova-driver removed: ironic |
To post a comment you must log in.
I suspect that this is not solvable in the current nova-scheduler architecture, and will require a mechanism for Ironic to actively inform Nova upon resource availability changes (rather than passively wait for Nova to request a list of available resources).
If/when that is possible, Ironic should add support for it.