Ask Your Question
0

Why do I get "NovaException: Unexpected vif_type=binding_failed" when setting up devstack Kilo with networking-ovs-dpdk and vxlan?

asked 2016-02-09 22:04:10 -0500

yby-developer gravatar image

I managed to load it on latest devstack (Mitaka). But when try the same thing on Kilo, whenever I instantiate a VM, I keep getting stuck on the error: NovaException: Unexpected vif_type=binding_failed. I've tried all answers online, and wasn't able to make this work.

This is the error on the controller:

2016-02-10 04:54:48.898 ERROR neutron.plugins.ml2.managers [req-78165d6e-1a3d-4083-a7c4-e55611b9597e neutron service] Failed to bind port 6533524a-2dac-42cc-ab7b-fd6932bf79e4 on host devsta
ck1-2
2016-02-10 04:54:48.899 ERROR neutron.plugins.ml2.managers [req-78165d6e-1a3d-4083-a7c4-e55611b9597e neutron service] Failed to bind port 6533524a-2dac-42cc-ab7b-fd6932bf79e4 on host devstack1-2

This is the error on the compute:

2016-02-10 04:54:52.486 ERROR nova.compute.manager [req-0df362c2-e3a1-4636-83df-ee31baef840d admin demo] [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd] Instance failed to spawn
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd] Traceback (most recent call last):
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]   File "/opt/stack/nova/nova/compute/manager.py", line 2473, in _build_resources
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]     yield resources
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]   File "/opt/stack/nova/nova/compute/manager.py", line 2345, in _build_and_run_inae
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]     block_device_info=block_device_info)
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]   File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2404, in spawn
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]     write_to_disk=True)
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]   File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 4205, in _get_guest_xml
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]     context)
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]   File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 4076, in _get_guest_coig
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]     flavor, virt_type)
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]   File "/opt/stack/nova/nova/virt/libvirt/vif.py", line 374, in get_config
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd]     _("Unexpected vif_type=%s") % vif_type)
2016-02-10 04:54:52.486 27939 TRACE nova.compute.manager [instance: 503365c6-7c07-4a83-bad0-f45c3f3e5dbd] NovaException: Unexpected vif_type=binding_failed

No other error in any other log.

My setup is:

1 controller+network node, Centos 7, devstack Kilo. No networking-ovs-dpdk.
2 compute nodes, Ubunto 14.04, devstack Kilo, networking-ovs-dpdk Kilo.
private network is vxlan.

Here is the relevant local.conf from the compute host:

disable_all_services

# Disable Nova-Network
disable_service n-net

enable_service n-cpu
enable_service rabbit
enable_service q-agt
enable_service n-novnc

Q_PLUGIN=ml2
Q_ML2_PLUGIN_MECHANISM_DRIVERS=ovsdpdk
Q_ML2_PLUGIN_TYPE_DRIVERS=flat,vlan,vxlan
Q_USE_SECGROUP=True
Q_L3_ENABLED=False
Q_USE_PROVIDER_NETWORKING=False
Q_ML2_TENANT_NETWORK_TYPE=vxlan
ENABLE_TENANT_VLANS=False
ENABLE_TENANT_TUNNELS=True
OVS_ENABLE_SG_FIREWALL_MULTICAST=False
OVS_PHYSICAL_BRIDGE=br-p1p1

enable_plugin networking-ovs-dpdk http://git.openstack.org/openstack/networking-ovs-dpdk stable/kilo

OVS_DPDK_INSTALL=True
SKIP_OVS_INSTALL=True
OVS_DATAPATH_TYPE=netdev
OVS_DPDK_RTE_LIBRTE_VHOST=y
OVS_DPDK_PORT_MAPPINGS=p1p1:br-p1p1
DPDK_PHYSICAL_NETWORK=dpdk-physical-net
OVS_BRIDGE_MAPPINGS+=,dpdk-physical-net:br-p1p1
OVS_NUM_HUGEPAGES=4096
OVS_SOCKET_MEM=1024 ...
(more)
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2016-02-10 11:56:55 -0500

yby-developer gravatar image

updated 2016-02-10 12:33:30 -0500

The error was actually resolved by adding the ovsdpdk mechanism driver to the controller as well.

sudo pip install -U networking-ovs-dpdk==1.2.0 Q_ML2_PLUGIN_MECHANISM_DRIVERS=openvswitch,ovsdpdk

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

1 follower

Stats

Asked: 2016-02-09 22:04:10 -0500

Seen: 487 times

Last updated: Feb 10 '16