if it was then the AggregateInstanceExtraSpecsFilter would work with it.
the only way to fix this is to deprecate teh use of hide_hypervisor_id and replace the namespaced version hw:hide_hypervisor_id or alter the AggregateInstanceExtraSpecsFilter to specifcly ignore that value.
but we also need the metadata keys to confirm.
note we also discussed some alteration to this filter and extra specs in general as part of the flavor extraspec validation work such as requireing the use of "aggregate_instance_extra_specs:..." going froward and removing support for unscoped extra specs.
this happens because when
the extra spec was intoduced by https:/ /blueprints. launchpad. net/nova/ +spec/hide- hypervisor- id-flavor- extra-spec
it failed to namespace the extra spec properly.
it should have been added to the hw: namespace.
if it was then the AggregateInstan ceExtraSpecsFil ter would work with it.
the only way to fix this is to deprecate teh use of hide_hypervisor_id and replace the namespaced version hw:hide_ hypervisor_ id or alter the AggregateInstan ceExtraSpecsFil ter to specifcly ignore that value.
but we also need the metadata keys to confirm.
note we also discussed some alteration to this filter and extra specs in general as part of the flavor extraspec validation work such as requireing the use of "aggregate_ instance_ extra_specs: ..." going froward and removing support for unscoped extra specs.