| 2019-05-22 17:47:31 |
Drew Freiberger |
description |
Upon enabling AggregateInstanceExtraSpecsFilter in nova-scheduler filters on a xenial-queens cloud, we found that instances were no longer being scheduled on any hosts. "No Valid Host was Found" error was found in nova logs.
The cause of this is that the flavors configured by nova-cloud-controller when related to nova-compute-kvm vs nova-compute-lxd charms creates flavors that are tagged for the different hypervisor_types.
This flavor ExtraSpec metadata needs to be classed/scoped against the proper capabilities filter, so that it does not match as a requirement when adding new *ExtraSpecs* filters such as AggregateInstanceExtraSpecsFilter.
To reproduce, deploy a typical cloud, xenial-queens, and add AggregateInstanceExtraSpecsFilter to the scheduler-default-filters on nova-cloud-controller charm, then you can see that it's not possible to deploy unless you either A) add "hypervisor_type=QEMU" (or LXD) to your aggregate, or remove the extra specs from the flavor, or re-classify the extra specs. |
Upon enabling AggregateInstanceExtraSpecsFilter in nova-scheduler filters on a xenial-queens cloud, we found that instances were no longer being scheduled on any hosts. "No Valid Host was Found" error was found in nova logs.
The cause of this is that the flavors configured by nova-cloud-controller when related to nova-compute-kvm vs nova-compute-lxd charms creates flavors that are tagged for the different hypervisor_types.
This flavor ExtraSpec metadata needs to be classed/scoped against the ComputeCapabilitiesFilter, so that it does not match as a requirement when adding new *ExtraSpecs* filters such as AggregateInstanceExtraSpecsFilter.
To reproduce, deploy a typical cloud, xenial-queens, and add AggregateInstanceExtraSpecsFilter to the scheduler-default-filters on nova-cloud-controller charm, then you can see that it's not possible to deploy unless you either A) add "hypervisor_type=QEMU" (or LXD) to your aggregate, or remove the extra specs from the flavor, or re-classify the extra specs with capabilities:hypervisor_type='QEMU'. |
|
