When enabling AggregateInstanceExtraSpecsFilter in scheduler-default-filters causes inability to deploy instances

Bug #1830099 reported by Drew Freiberger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Nova Cloud Controller Charm
Triaged
Low
Unassigned

Bug 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 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'.

description: updated
Revision history for this message
Drew Freiberger (afreiberger) wrote :
Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

LXD is no longer a supported hypervisor, so this shouldn't impact things going forward. Making it low in case a backport is needed for an existing deployed system.

Changed in charm-nova-cloud-controller:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

I got same issues on Xenial + Ocata.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.