Instance failing to spawn, logs show `NovaException: Unexpected vif_type=binding_failed`

asked 2014-09-24 19:44:50 -0600

Liam Haworth gravatar image

updated 2014-09-24 20:02:06 -0600

larsks gravatar image

Afternoon Openstack,

I have hit a problem that has been plaguing me for the past week and a bit, the problem is bellow

2014-09-24 13:35:48.870 2059 ERROR nova.scheduler.filter_scheduler [req-fe9e85a9-b5d2-4977-8f73-dd9d7be3911f 355b18b008fe4fe0a8ab88131cc2b41c 42dac9f04b374fecb0dc48ddba89a2f3] [instance: d9b3c4d7-5331-490c-9cae-9084f391fda2] Error from last host: vmhost3 (node [u'Traceback (most recent call last):\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/compute/", line 1329, in _build_instance\n    set_access_ip=set_access_ip)\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/compute/", line 393, in decorated_function\n    return function(self, context, *args, **kwargs)\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/compute/", line 1741, in _spawn\n    LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/openstack/common/", line 68, in __exit__\n    six.reraise(self.type_, self.value, self.tb)\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/compute/", line 1738, in _spawn\n    block_device_info)\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/", line 2284, in spawn\n    write_to_disk=True)\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/", line 3478, in to_xml\n    disk_info, rescue, block_device_info)\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/", line 3292, in get_guest_config\n    flavor)\n', 
u'  File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/", line 384, in get_config\n    _("Unexpected vif_type=%s") % vif_type)\n', u'NovaException: Unexpected vif_type=binding_failed\n']

Since that is really a wall of text, here is a TL;DR of the error NovaException: Unexpected vif_type=binding_failed.

Yes, all agents are running:

| id       ...|     agent_type     | host    | alive | admin_state_up |  
| 0b370b66-...| Open vSwitch agent | os-net  | :-)   | True           |  
| 2011c9d5-...| L3 agent           | os-net  | :-)   | True           |  
| 351cd9d8-...| Open vSwitch agent | vmhost3 | :-)   | True           |  
| 861258be-...| Metadata agent     | os-net  | :-)   | True           |  
| b71622ce-...| DHCP agent         | os-net  | :-)   | True           |  

And, yes, all the ML2 and neutron configs are setup correctly, but just in case.

Control Node:
Network Node:
Compute Node:

If there is anything else I need to put to help debug I can.

Any and all help is welcome and thanked!

edit retag flag offensive close merge delete


The vif_type=binding failed message often indicates a problem with your Neutron configuration. Examine the neutron logs on your compute hosts and on your controller(s) to see if there are any errors that correspond to the timestamps in the compute log.

larsks gravatar imagelarsks ( 2014-09-24 19:59:38 -0600 )edit

Just spun up a VM while watching the neutron logs on both servers, no errors were thrown in them. But if I do the same thing but watch the nova logs instead the error shows there. I really have no clue why this is happening o_O

Liam Haworth gravatar imageLiam Haworth ( 2014-09-24 20:07:08 -0600 )edit

Just to be "both servers", do you mean "all three servers"? If you restart neutron services, are there any errors/tracebacks/etc at the time the service starts?

larsks gravatar imagelarsks ( 2014-09-24 20:12:41 -0600 )edit

Ok, I stopped all neutron services on all servers, cleaned out the logs, started the services again and tailed all the logs, I ended up finding this on the compute node.

Liam Haworth gravatar imageLiam Haworth ( 2014-09-24 20:27:11 -0600 )edit

It looks like openvswitch has not been started.

larsks gravatar imagelarsks ( 2014-09-24 20:33:49 -0600 )edit

3 answers

Sort by ยป oldest newest most voted

answered 2014-09-24 22:24:56 -0600

Liam Haworth gravatar image

updated 2014-09-25 08:16:40 -0600

larsks gravatar image

I have found the problem, after searching deeper I found that the ports weren't binding so I searched that error and this this question

I have a look at my own /etc/init/neutron-server.conf file and saw that mine two was not loading the ml2 config file, I add a line to make it load the config file and bam! Its working now.

Thank you for all the help Iarsks!

edit flag offensive delete link more


Glad you got it working!

larsks gravatar imagelarsks ( 2014-09-25 08:16:29 -0600 )edit

can you share what exactly you added in /etc/init/neutron-server.conf file

vikrant gravatar imagevikrant ( 2014-11-26 05:22:36 -0600 )edit


I am getting this error in Juno release. i am using gre in 3 node setup. Getting error log in nova-compute.log, other logs are fine.

vikrant gravatar imagevikrant ( 2014-11-27 05:29:05 -0600 )edit

Instance is not getting ip from dhcp with VLAN network type in OPENSUSE+Icehouse

Raghavachari gravatar imageRaghavachari ( 2014-12-04 08:49:52 -0600 )edit

I followed and done:

crudini --set /etc/neutron/neutron.conf DEFAULT core_plugin neutron.plugins.ml2.plugin.Ml2Plugin
crudini --set /etc/neutron/neutron.conf DEFAULT service_plugins
msuchy gravatar imagemsuchy ( 2015-02-20 07:03:06 -0600 )edit

answered 2015-06-22 21:41:08 -0600

GfengWong gravatar image

updated 2015-06-22 21:45:10 -0600

Have you resolved?I also stopped by the question.My configuration is correct

edit flag offensive delete link more

answered 2015-02-19 02:04:31 -0600

Janki gravatar image

Can you share the changes you made? I am facing the same error..

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2014-09-24 19:44:50 -0600

Seen: 26,687 times

Last updated: Jun 22 '15