Comment 2 for bug 1841932

Actually, wait, what were the metadata values on the host aggregate you're trying to use? Looking at the code, it handles unscoped extra specs and should be looking for an aggregate metadata key of "hide_hypervisor_id" that matches the flavor extra spec key.

Can you enable debugging in the scheduler service and recreate this and provide the logs that show the filter rejecting the instance using that flavor?