# Unexpected vif_type=binding_failed

Hi Guys,

really frustrating today. :( . i just bring up 2 server 1 for controller + 1 for compute server using KILO. i try almost all the solution that i can find today and all did not solve my issue.

when i spawn instance, i will get error as per my title. and when i check inside neutron logs. i find below errors.

 ERROR neutron.plugins.ml2.managers [req-07dee475-6386-4a43-9837-1ac41b711938 ] Failed to bind port b75bec9c-cc80-4a3f-ab02-2427ce2bb77d on host 172.16.21.6
2015-05-23 18:52:00.096 25883 ERROR neutron.plugins.ml2.managers [req-07dee475-6386-4a43-9837-1ac41b711938 ] Failed to bind port b75bec9c-cc80-4a3f-ab02-2427ce2bb77d on host 172.16.21.6


probably i was thinking it is cause by br-int bridge. like i said, i test almost all the solution that i can find but still no luck.

what confusing me is, i'm able to create router attached interface to the router and it is able to reach the internet. even i attached internal network without having any issue. but when i try to attached the network to the instance, i will get the above error. this one really crack my head. :)

also we can see inside ovs-vswitchd.log below error, this keep repeating when we add additional network:

netdev_linux|INFO|ioctl(SIOCGIFHWADDR) on tap49bbfdd0-7d device failed: No such device
netdev_linux|WARN|ioctl(SIOCGIFINDEX) on tap49bbfdd0-7d device failed: No such device


this only gone away once i set both dhcp_agent.ini and l3_agent.ini configuration for ovs_use_veth = True.

please find below is my ml2_agent config:

[ml2]
# (ListOpt) List of network type driver entrypoints to be loaded from
# the neutron.ml2.type_drivers namespace.
#
# type_drivers = local,flat,vlan,gre,vxlan
# Example: type_drivers = flat,vlan,gre,vxlan
type_drivers = flat,vlan,gre,vxlan

# (ListOpt) Ordered list of network_types to allocate as tenant
# networks. The default value 'local' is useful for single-box testing
# but provides no connectivity between hosts.
#
# tenant_network_types = local
# Example: tenant_network_types = vlan,gre,vxlan
tenant_network_types = gre

# (ListOpt) Ordered list of networking mechanism driver entrypoints
# to be loaded from the neutron.ml2.mechanism_drivers namespace.
# mechanism_drivers =
# Example: mechanism_drivers = openvswitch,mlnx
# Example: mechanism_drivers = arista
# Example: mechanism_drivers = cisco,logger

# (ListOpt) Ordered list of extension driver entrypoints
# to be loaded from the neutron.ml2.extension_drivers namespace.
# extension_drivers =
# Example: extension_drivers = anewextensiondriver

# (IntOpt) Path MTU.  The maximum permissible size of an unfragmented
# packet travelling from and to addresses where encapsulated Neutron
# traffic is sent.  Drivers calculate maximum viable MTU for
# validating tenant requests based on this value (typically,
# path_mtu - max encap header size).  If <=0, the path MTU is
# indeterminate and no calculation takes place.
# path_mtu = 0

# (IntOpt) Segment MTU.  The maximum permissible size of an
# unfragmented packet travelling a L2 network segment.  If <=0,
# the segment MTU is indeterminate and no calculation takes place.
# segment_mtu = 0

# (ListOpt) Physical network MTUs.  List of mappings of physical
# network to MTU value.  The format of the mapping is
# <physnet>:<mtu val>.  This mapping allows specifying a
# physical network MTU value that differs from the default
# segment_mtu value ...
edit retag close merge delete

please post you ml2_conf.ini and the output of neutron agent-show for the agent on the compute node

Additionally, what type of network are you starting the instance on? flat, vlan, vxlan, gre?

( 2015-05-24 04:10:39 -0500 )edit

Hi Sam, i have edit my question and added the information that you need. i use gre. for external i use flat or vlan.

( 2015-05-24 18:50:03 -0500 )edit

Sort by » oldest newest most voted

I've seen similar issues when Neutron is not configured to send notification to Nova properly, there are also some types of setup not supporting this, I think it was a DVR setup.

Please post your configuration for neutron and nova and outputs of i.e neutron agent-show, nova service-list.

As a simple test, please try to do the following change in nova.conf. This is not recommended but maybe will solve the issue that you can't boot your instance.

vif_plugging_is_fatal=false
vif_plugging_timeout=5


Best regards

more

Hi tobasco, yerp already try this. because my last implementation for juno i remember adding this will solve the interface creation issue. but i find it not for kilo or might be i did something wrong. :)

( 2015-05-24 18:51:24 -0500 )edit

hi,

even i encountered this problem after all the debugging what solved problem for me is the following.

ovs-vsctl show   this command returns some value like br-int, br-tun


bridge br-int is not able to assign appropriate port to VM, so i removed br-int and once again added and it worked for me.

hope that helps you.

more

Hi Pradeep, you are lucky. i try that for couple of time and also reboot the server. still not solve my problem.

( 2015-05-25 00:52:31 -0500 )edit

Hi Guys, i'm not sure why. the issue resolve after i reimage the whole server and use the same config again. :)

more