hide_hypervisor_id extra_specs in nova flavor cannot pass AggregateInstanceExtraSpecsFilter
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Stephen Finucane | ||
Train |
Fix Released
|
Undecided
|
Unassigned | ||
Ussuri |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Description
===========
when we enable nova AggregateInstan
See the codes below:
# Either not scope format, or aggregate_
scope = key.split(':', 1)
if len(scope) > 1:
if scope[0] != _SCOPE:
key = scope[0]
Steps to reproduce
==================
in nova.conf
[filter_scheduler]
enabled_filters = ....,AggregateI
create a flavor like "g3.8xlarge" and setting extra_specs "hide_hyperviso
nova flavor-key g3.8xlarge set hide_hypervisor
then create a instance with flavor g3.8xlarge, it will report "Filter AggregateInstan
Environment
===========
(nova-scheduler
openstack-
openstack-
python-
python2-
I think this is a BUG in AggregateInstan
Changed in nova: | |
status: | Expired → New |
Changed in nova: | |
assignee: | Jie Li (ramboman) → Stephen Finucane (stephenfinucane) |
Changed in nova: | |
assignee: | Stephen Finucane (stephenfinucane) → Jie Li (ramboman) |
Changed in nova: | |
assignee: | Jie Li (ramboman) → Stephen Finucane (stephenfinucane) |
Yeah I think the problem is the hide_hypervisor_id extra spec doesn't have something like the "os:" prefix. I don't think removing the scope checking in the filter is an option since that would break behavior for existing flavors that are properly scoped. So what we'd probably have to either do is (1) add compat for os:hide_ hypervisor_ id and reference that in docs and code or (2) just hard-code a check in the filter itself for that extra spec which is easy but gross.