Ask Your Question
0

Device $UUID not defined in plugin, Unexpected vif_type=binding_failed, cannot launch instances

asked 2015-04-06 16:09:45 -0500

rlrevell gravatar image

updated 2015-04-07 08:23:45 -0500

I have tried every suggestion I can find to solve this problem: destroy and rebuild the network node, drop and recreate the neutron database, delete and recreate networks, delete and recreate OVS bridges, and it still persists.

I think the problem begins when I create the router:

# neutron router-interface-add demo-router demo-subnet
Added interface ad20d4ed-aa62-4223-9ed5-4d1a7def07dd to router demo-router.

This causes the following on the network node:

2015-04-06 17:00:46.742 2779 WARNING neutron.plugins.openvswitch.agent.ovs_neutron_agent [req-0bf50bd6-1c75-4d5c-9bd8-1bfc87977248 None] Device ad20d4ed-aa62-4223-9ed5-4d1a7def07dd not defined on plugin

# neutron router-gateway-set demo-router ext-net
Set gateway for router demo-router

Causes:

2015-04-06 17:00:46.742 2779 WARNING neutron.plugins.openvswitch.agent.ovs_neutron_agent [req-0bf50bd6-1c75-4d5c-9bd8-1bfc87977248 None] Device ad20d4ed-aa62-4223-9ed5-4d1a7def07dd not defined on plugin

Launching an instance does not work; the network node logs the "not defined on plugin" error, the instance creation fails with "no valid host was found", and in the logs of the compute node I see the dreaded "Unexpected vif_type=binding_failed" message.

vif_plugging_is_fatal=false
vif_plugging_timeout=0

does not help, all instance creations still fail with "No valid host was found"

I have this all working perfectly in a virtualized environment and I have repeatedly checked the configs of controller node, network node, and compute node and they are identical to the working environment except for different IPs and hostnames.

Edit: added requested info

# egrep -v ^#\|^$ /etc/neutron/plugins/ml2/ml2_conf.ini 
[ml2]
type_drivers = flat,gre
tenant_network_types = gre
mechanism_drivers = openvswitch
[ml2_type_flat]
flat_networks = external
[ml2_type_vlan]
[ml2_type_gre]
tunnel_id_ranges = 1:1000
[ml2_type_vxlan]
[securitygroup]
enable_security_group = True
enable_ipset = True
firewall_driver = neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
[ovs]
local_ip = 10.0.0.53
enable_tunneling = True
bridge_mappings = external:br-ex
[agent]
tunnel_types = gre

# ovs-vsctl show
d3798e19-b7d2-4b97-8532-7d1a8ba40389
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
        Port "em3"
            Interface "em3"
        Port "qg-0826cdac-08"
            Interface "qg-0826cdac-08"
                type: internal
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port "gre-0a000033"
            Interface "gre-0a000033"
                type: gre
                options: {df_default="true", in_key=flow, local_ip="10.0.0.53", out_key=flow, remote_ip="10.0.0.51"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge br-int
        fail_mode: secure
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port "tap28899b2f-6d"
            tag: 4095
            Interface "tap28899b2f-6d"
                type: internal
        Port "qr-ad20d4ed-aa"
            tag: 4095
            Interface "qr-ad20d4ed-aa"
                type: internal
    ovs_version: "2.0.2"
edit retag flag offensive close merge delete

Comments

Please, provide ml2_conf.ini && ovs-vsctl show on Network Node.

dbaxps gravatar imagedbaxps ( 2015-04-07 00:31:32 -0500 )edit

4 answers

Sort by ยป oldest newest most voted
0

answered 2015-09-04 12:59:04 -0500

Kairo gravatar image

Some news about this problem? I have the same problem.

edit flag offensive delete link more
0

answered 2015-09-06 23:40:04 -0500

smcas gravatar image

hiii, rirevell https://ask.openstack.org/en/question... see this link.It may help you

edit flag offensive delete link more
0

answered 2015-04-07 08:36:47 -0500

dbaxps gravatar image

updated 2015-04-07 08:47:32 -0500

You have tag 4095. It is symptom of dead tag .

   Port "tap28899b2f-6d"
            tag: 4095
            Interface "tap28899b2f-6d"

   Port "qr-ad20d4ed-aa"
             tag: 4095
             Interface "qr-ad20d4ed-aa"

private network won't work. Try recreate it and interface at router.
Also recreate ext-net qr-xxxxx is interface of ext-net
Check for tag 4095 afterwards in ovs-vsctl show

edit flag offensive delete link more

Comments

I've recreated everything more than once - all networks, router, even uninstalled and reinstalled openvswitch (on the network node that is). No change. Could there be some state persisting that isn't apparent (like in database or on another node)?

rlrevell gravatar imagerlrevell ( 2015-04-07 08:47:12 -0500 )edit

Every time tag 4095 came up. Am I correct ?

dbaxps gravatar imagedbaxps ( 2015-04-07 08:49:57 -0500 )edit

Please, run on controller :-

nova-manage service list
neutron agent-list
dbaxps gravatar imagedbaxps ( 2015-04-07 08:54:43 -0500 )edit

I did find one configuration bug on compute node (wrong controller hostname in neutron.conf) but fixing it did not affect this problem. Current output of the above commands:

output

rlrevell gravatar imagerlrevell ( 2015-04-07 10:02:03 -0500 )edit

Sorry to ask you again, does tag 4095 comes up on regular basic after you recreate networks && interfaces at router && router itself or I noticed it by chance ?

dbaxps gravatar imagedbaxps ( 2015-04-07 10:14:24 -0500 )edit
0

answered 2015-04-08 10:07:32 -0500

rlrevell gravatar image

updated 2015-04-08 13:28:15 -0500

Update: A teardown and reinstall solved this problem.

My working theory is that the issue had something to do with my initially forgetting to install neutron-plugin-ml2 on the controller node before populating the neutron database, as the doc states that "Database population occurs later for Networking because the script requires complete server and plug-in configuration files". I suspect this led to a database inconsistency that dropping and recreating the neutron database did not fix.

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: 2015-04-06 16:09:45 -0500

Seen: 2,926 times

Last updated: Sep 06 '15