Assuming you are using neutron, do neutron agent-list on your controller node. This should list the neutron agent on your compute nodes. There can be a few possibilities after you have issued this command:

1. Your neutron agent for the compute host is not listed - it means - your agent was never successful in registering itself to the neutron server on your controller node. check the server.log file under /var/log/neutron for more information on this along with the compute node logs under /var/log/neutron. Ensure that your compute and controller nodes don't have a time offset.

2. You have a XXX marked against your neutron agent. This means - your AMQP is probably broken, this is unlikely because you seem to have registered your compute hosts just fine.

3. You have neither of 1 or 2, in such a case, when you deploy the VM - check your neutron server.log file when you fire the deploy operation. One of the reasons for failure could be that your agent isn't using the right network types as expected by ML2. That is - if ML2 allows only vlan, vxlan but you are trying to register a gre based network - it would fail.

Hope this helps!

3.

Do you have any metadata attached to your glance image?, From the looks of the error. the attempt to run a vm on the instance but fails, the reason for the failure is Unexpected vif_type=binding_failed It may be best to check nova network or neutron-ovs to see if there are errors with the port creation

Set scheduler_default_filters=AllHostsFilter in nova.conf and restart nova services.