Ask Your Question
0

Error: Failed to launch instance "admin_instance": Please try again later [Error: Unexpected vif_type=binding_failed]

asked 2014-05-09 14:37:22 -0500

david gravatar image

updated 2014-05-09 15:47:55 -0500

I am installing OpenStack icehouse on 4 VMs (1 controller node, 1 networking node and 2 compute nodes) running on HP server with ESXi 5.0 hypervisor for a school project.

Below is a log on the dashboard when I tried launching an instance:

Message: Unexpected vif_type=binding_failed

Code: 500

Details

File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 296, in decorated_function return function(self, context, *args, **kwargs) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2075, in run_instance do_run_instance() File "/usr/lib/python2.7/dist-packages/nova/openstack/common/lockutils.py", line 249, in inner return f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2074, in do_run_instance legacy_bdm_in_spec) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1207, in _run_instance notify("error", fault=e) # notify that build failed File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1191, in _run_instance instance, image_meta, legacy_bdm_in_spec) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1355, in _build_instance filter_properties, bdms, legacy_bdm_in_spec) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1401, in _reschedule_or_error self._log_original_error(exc_info, instance_uuid) File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1396, in _reschedule_or_error bdms, requested_networks) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2125, in _shutdown_instance requested_networks) File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 68, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2115, in _shutdown_instance block_device_info) File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 953, in destroy destroy_disks) File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 989, in cleanup self.unplug_vifs(instance, network_info) File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 860, in unplug_vifs self.vif_driver.unplug(instance, vif) File "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/vif.py", line 798, in unplug _("Unexpected vif_type=%s") % vif_type)

I have been stuck with the problem for about 2 days and I have tried going over the installation steps again but could not find any solution. Please, I need help.

Thank you.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2014-05-20 11:55:17 -0500

fgorbat gravatar image

Had similar issue with the "Error: Unexpected vif_type=binding_failed" after upgrading of the openvswitch-agent rpm. Fixing done according to the installation http://docs.openstack.org/icehouse/install-guide/install/yum/content/neutron-ml2-network-node.html (http://docs.openstack.org/icehouse/in...) guide.

Due to a packaging bug, the Open vSwitch agent initialization script explicitly looks for the Open vSwitch plug-in configuration file rather than a symbolic link /etc/neutron/plugin.ini pointing to the ML2 plug-in configuration file. Run the following commands to resolve this issue:

cp /etc/init.d/neutron-openvswitch-agent /etc/init.d/neutron-openvswitch-agent.orig
sed -i 's,plugins/openvswitch/ovs_neutron_plugin.ini,plugin.ini,g' /etc/init.d/neutron-openvswitch-agent
edit flag offensive delete link more
0

answered 2014-05-12 10:25:38 -0500

I have a similar issue here when adding a new compute node to an existing Havana OpenStack cluster on KVM. When I do a nova boot cirros image, I got the same error as David. If any one can give us some other idea to check, it is much appreciated. I did some basic sanity check as described below.

David: I checked my ml2_conf.ini, it is set in the same style as the existing and working compute node. neutron agent-list shows OVS agent is running properly. nova service-list should also shows that nova is running on your compute. These 3 are the basic things you need to check first.

edit flag offensive delete link more

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

Stats

Asked: 2014-05-09 14:37:22 -0500

Seen: 1,660 times

Last updated: May 20 '14