Ask Your Question
2

Instance fails to spawn with Unexpected vif_type=binding_failed [closed]

asked 2014-09-15 19:40:42 -0500

TVA gravatar image

updated 2014-09-17 11:11:46 -0500

I've seen a number of questions around issues with Icehouse producing NovaException: Unexpected vif_type=binding_failed. There have been a number of suggestions none of which worked for me so hoping someone can tell me what I'm missing here. I'm running a 4 node configuration controller, network, compute & block storage.

Nova-compute.log extract from compute node

[req-ba14f463-787c-4daa-b611-0a0f32f0957a 78a136070de24f73b60017a8cd794806 02b9da74025a440cb64f142438d38c40] [instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff] Instance failed to spawn
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff] Traceback (most recent call last):
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1738, in _spawn
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]     block_device_info)
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2284, in spawn
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]     write_to_disk=True)
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3478, in to_xml
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]     disk_info, rescue, block_device_info)
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3292, in get_guest_config
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]     flavor)
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]   File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 384, in get_config
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]     _("Unexpected vif_type=%s") % vif_type)
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff] NovaException: Unexpected vif_type=binding_failed
[instance: 5b4f8680-6f8a-46b7-9b1b-cc3b7cdb50ff]

nova.conf from compute node

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by TVA
close date 2014-10-16 22:18:04.311843

Comments

What are the suggestions of which none worked for you? If you can tell us what you've looked at we can avoid suggesting things you've already tried.

larsks gravatar imagelarsks ( 2014-09-15 21:29:38 -0500 )edit

Sorry good point. 1. https://bugs.launchpad.net/neutron/+b... (checked conf file included fixes) 2. https://ask.openstack.org/en/question... (added suggested libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtGenericVIFDriver to nova.conf on compute node)

TVA gravatar imageTVA ( 2014-09-16 17:26:37 -0500 )edit
  1. Tried the suggestion: https://ask.openstack.org/en/question... without success. Found both options are valid dependent on section see: http://docs.openstack.org/trunk/confi...
TVA gravatar imageTVA ( 2014-09-18 20:01:57 -0500 )edit

1 answer

Sort by ยป oldest newest most voted
2

answered 2014-09-15 23:51:08 -0500

Most likely your bridges need to be recreated on your compute nodes. I ran into exact same issue after running "yum update" on two of my compute nodes, and started getting same error on both nodes.

I end up running the following commands to get it back...

ovs-vsctl del-br br-int
ovs-vsctl add-br br-int

I recommend a reboot after running these commands.

edit flag offensive delete link more

Comments

Thanks Yellow circle. I tried your suggestion same issue but I do get a new info/error mesg from neutron api in the nova log " INFO nova.network.neutronv2.api - Unable to reset device ID for port None" so progress. There wasn't a corresponding error/info mesg in openvswitch-agent.log.

TVA gravatar imageTVA ( 2014-09-16 17:32:32 -0500 )edit

The bridge was definitely the cause of the issue. It took a reinstall to get it running.

TVA gravatar imageTVA ( 2014-10-16 22:21:27 -0500 )edit

I tried to do the same what you mentioned above , but that bridge is not deleted or i also tried to delete port inside that br but not successful .

chintan gravatar imagechintan ( 2014-11-17 07:00:15 -0500 )edit

I am also unable to delete that br-int bridge using "ovs-vsctl del-br br-int". Any suggestions as to how did you resolve this issue

DarkKnight gravatar imageDarkKnight ( 2015-08-24 02:09:55 -0500 )edit

I can delete br-int but the issue still remain. thank.

sawangpongm gravatar imagesawangpongm ( 2015-11-30 10:13:37 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-09-15 19:40:42 -0500

Seen: 10,070 times

Last updated: Sep 17 '14