Report client can try to ensure a standard resource class
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Eric Fried |
Bug Description
SchedulerReport
The problem is that this relies on the local system's notion of the set of standard resource classes. If the placement service is running newer code, standard resource classes may have been added that the compute service doesn't know about yet. If a consumer attempts to use such a resource class, the above block will attempt to _ensure_
We should never be relying on placement code directly on the compute node. (This includes introspecting os-traits.) We should always be asking the placement service.
Fix proposed to branch: master /review. openstack. org/539732
Review: https:/