New Question

Revision history [back]

click to hide/show revision 1
initial version


The warning you've mentioned in the Hyper-V nova-compute logs has nothing to do with not being able to spawn instances.

The error you've mentioned in the title is a nova-scheduler typical error, meaning that it could not find a proper host for your request. If the ImagePropertiesFilter filter failed, it probably means that the image you're trying to use doesn't have the right properties for Hyper-V (hypervisor_type=hyperv, disk-format=vhd).

A few other things to keep in mind:

  • Since you're using Ocata, you have to be extra careful when adding new compute nodes. Nova cells became mandatory in Ocata, and new compute nodes are not mapped to any nova cell and will be ignored by the nova-scheduler. After you've mapped the new compute nodes to nova cells, you'll need to restart the nova-scheduler and placement-api services in order for them to be taken into account.

  • One common mistake is using VXLAN neutron networks while the Hyper-V compute nodes only have Neutron Hyper-V Agent as an L2 agent. This agent does not support VXLAN, and you should use Windows OVS and the neutron-ovs-agent [1]. This agent and its necessary configurations are automatically created by our OpenStack Nova Installer starting with the Pike release.

  • If you are using VLAN neutron networks, then the Neutron Hyper-V Agent will be just fine, just keep in mind that you'll have to configure your Neutron controller to use the hyperv mechanism_driver by editing the file /etc/neutron/plugins/ml2/ml2_conf.ini, installing networking-hyperv (pip install networking-hyperv==4.0.0 - 4.0.0 is the released version for Ocata), and restart your neutron-server service. If you check the neutron-server logs, you should see that the hyperv mechanism driver has been initialized. For more details, check [2]



Best regards,

Claudiu Belu