Placement is not aware of disabled compute nodes
Bug #1805984 reported by
Belmiro Moreira
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Matt Riedemann |
Bug Description
Placement doesn't know if a resource provider (in this particular case a compute node) is disabled. This is only filtered by the scheduler using the "ComputeFilter".
However, when using the option "max_placement_
There are several use-cases when an operator may want to disable nodes to avoid the creation of new VMs.
Related with: https:/
Changed in nova: | |
assignee: | Matt Riedemann (mriedem) → Eric Fried (efried) |
summary: |
- Placement is not aware of disable compute nodes + Placement is not aware of disabled compute nodes |
Changed in nova: | |
assignee: | Eric Fried (efried) → Matt Riedemann (mriedem) |
To post a comment you must log in.
knowledge of the status of openstack service is currently not within the scope of placement to track.
it is undesirable however to get a No Valid host from the nova api due to the presence of downed compute nodes in the placement response.
i have triage this as whishlist as i think this is functioning as desinged but this is an unfortunate edgecase taht would
be better addressed by a spec or a specless blueprint.
i think its unlikely that you would have enough hosts marked as down for this to typically be an issue but in large deployments
this becomes more likely.