Ask Your Question

Unable to launch instances (Unexpected vif_type=binding failed)

asked 2015-08-21 06:58:44 -0500

DarkKnight gravatar image

updated 2015-08-21 07:07:03 -0500

dbaxps gravatar image

Hi Community,

A lot many people have stopped by at the same error. I am trying to install openstack(3 node installation setup). When i try to create instances using the dashboard, i get a failure. Here is what i get in the nova-compute log.


2015-08-21 22:55:00.391 41235 TRACE nova.compute.manager [instance: d9bfa207-6e85-4ca8-a385-52d90818a49b]     _("Unexpected vif_type=%s") % vif_type)
2015-08-21 22:55:00.391 41235 TRACE nova.compute.manager [instance: d9bfa207-6e85-4ca8-a385-52d90818a49b] NovaException: Unexpected vif_type=binding_failed

Have gone through all the similar questions on the forum, but unfortunately none of them have solved the issue for me. Have checked all the configuration files incessant number of times for any errors but to no avail. Some of these questions links that i went through are

Some of these answers are suggesting "Has created the tunnel in between Compute and Neutron and mapping the bridge communication" as the solution. But none of them have been kind enough to list the exact set of steps to do that.

Some of those answers have also suggested that deletion of the br-ex bridge and then manual creation will do. but when i try to delete the br-ex bridge . the bridge is not removed.

Can anyone suggest the set of steps that one need to do.

Thanking all of you lovely members in anticipation that the steps shall be suggested, or at least references to appropriate blogs on this issue will be given.

edit retag flag offensive close merge delete


Forgot to tell the underlying OS is Centos 7 and have religiously followed the docs at One more thing the compute and controller are not synced in time. Could that be an issue too?

DarkKnight gravatar imageDarkKnight ( 2015-08-21 07:00:23 -0500 )edit

4 answers

Sort by ยป oldest newest most voted

answered 2015-08-25 23:40:35 -0500

DarkKnight gravatar image

OK! i got a work-around, but i still dont know what was causing the issue in the previous case. I created another network( to be used by the instances. Earlier was ( Now whenever i use my second network to be used to create instances(12 series), the instance successfully launches. If i return back to using the earlier network(203 series), i again get the same error. "Binding failed!! Unexpected VIF_Type"

Here are my network interfaces []

Can anyone suggest anything on this?

edit flag offensive delete link more


I had exactly same problem and your answer worked in my case. Its weird that there is no solid reason behind it. Thanks anyway.

Shankar Lal gravatar imageShankar Lal ( 2016-01-13 03:28:20 -0500 )edit

answered 2016-06-15 10:26:21 -0500

6543217890meh gravatar image

updated 2016-06-15 10:27:07 -0500

I have run into this issue and tried all of the suggestions without any luck. I decided to upgrade the python-neutronclient using pip and this solved my bind ERRORs. Also many other issues seem to be solved by doing an apt-get upgrade after installing all the components. You would think the install would install the most recent version, but doing an upgrade on all of my components finds things to upgrade and install. I am running Liberty on Ubuntu 14.04. This suggestion has helped when everything in my config files looks good, but things are still not working.

edit flag offensive delete link more

answered 2015-08-23 21:51:38 -0500

sculiuyun gravatar image

updated 2015-08-23 22:15:03 -0500

Try to Edit /etc/nova/nova.conf on compute node,and add the follow configuration.

vif_plugging_timeout= 0

Then restart nova-conpute service.

service nova-compute restart
edit flag offensive delete link more


Does not help!! tried adding these lines in the /etc/nova/nova.conf file, still gives the same error "NO valid host was found!" and the nova-compute log still has the same error

DarkKnight gravatar imageDarkKnight ( 2015-08-23 23:42:34 -0500 )edit

Could you paste you configure file about nova.conf and nova-compute.conf here on compute node?

sculiuyun gravatar imagesculiuyun ( 2015-08-24 00:18:16 -0500 )edit : Nova.conf file on the compute node. Let me know in case you need to have a look at the remaining conf files

DarkKnight gravatar imageDarkKnight ( 2015-08-24 01:00:17 -0500 )edit

i have seen this problem surfacing for many people till now, but no solution proposed that could solve this. Anyone please????

DarkKnight gravatar imageDarkKnight ( 2015-08-24 02:30:59 -0500 )edit

Sorry , I have seen your configure file,but I can't find something wrong!!

sculiuyun gravatar imagesculiuyun ( 2015-08-24 03:05:56 -0500 )edit

answered 2016-06-16 04:55:13 -0500

Sanjay_1987 gravatar image

updated 2016-06-16 04:57:31 -0500

Hello, Faced the same issue with Mitaka. Problem was that openvswitch agent was not using ml2_conf.ini file. When i do ps -eaf|grep neutron-openv , i can see that its not using ml2_conf file as config file. Only openvswitch_agent.ini file is there. *

/usr/bin/neutron-openvswitch-agent --config-file=/etc/neutron/neutron.conf --config-file=/etc/neutron/plugins/ml2/openvswitch_agent.ini --log-file=/var/log/neutron/openvswitch-agent.log


I stopped the service on both compute and network node by: service neutron-openvswitch-agent stop and added "--config-file=/etc/neutron/plugins/ml2/ml2_conf.ini" to manually run it on both nodes using:

/usr/bin/neutron-openvswitch-agent --config-file=/etc/neutron/neutron.conf --config-file=/etc/neutron/plugins/ml2/openvswitch_agent.ini --config-file=/etc/neutron/plugins/ml2/ml2_conf.ini --log-file=/var/log/neutron/openvswitch-agent.log

Hope this helps

edit flag offensive delete link more


please refer: (

Sanjay_1987 gravatar imageSanjay_1987 ( 2016-06-16 04:58:47 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2015-08-21 06:58:44 -0500

Seen: 2,837 times

Last updated: Jun 16 '16