[openstack-dev] [ansible] One or more undefined variables: 'dict object' has no attribute 'bridge'

Kevin Carter kevin.carter at RACKSPACE.COM
Mon Dec 14 15:46:46 UTC 2015


The port binding issues are usually related to a neutron physical interface mapping issue however based on your previous config I don't think that was the problem. If you're deploying Liberty/Master(Mitaka) there was was a fix that went in that resolved an issue within neutron and the use of L2/multicast groups [0] and if your on the stable tag the fix has not been released yet and will be there for the 12.0.3 tag, coming soon. To resolve the issue the fix is to simply to add the following to your `user_variables.yml` file:

== If you don't want to use l2 population add the following ==
neutron_l2_population: "False"
neutron_vxlan_group: "239.1.1.1"
 
== If you want to use l2 population add the following ==
neutron_l2_population: "True"

As for the neutron services on your compute nodes, they should be running within the host namespace. In liberty/Master the python bits will be within a vent using an upstart init script to control the service. If your not seeing the neutron service running its likely due to this bug [2] which is resolve by dropping the previously mentioned user variable options. 

I hope this helps and let me know how it goes. 

[0] https://review.openstack.org/#/c/255624
[1] https://github.com/openstack/openstack-ansible/commits/liberty
[2] https://bugs.launchpad.net/neutron/+bug/1470584

--

Kevin Carter
IRC: cloudnull


________________________________________
From: Mark Korondi <korondi.mark at gmail.com>
Sent: Sunday, December 13, 2015 9:10 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [ansible] One or more undefined variables: 'dict object' has no attribute 'bridge'

Thanks cloudnull,

This solved the installation issue. I commented out all non-flat
related networks before, to investigate my main problem, which is

> PortBindingFailed: Binding failed for port fe67a2d5-6d6a-4440-80d0-acbe2ff5c27f, please check neutron logs for more information.

I still have this problem; I created the flat external network with no
errors, still I get this when trying to launch an instance. What's
really interesting to me, is that no neutron microservices are
deployed and running on the compute node.

Mark (kmARC)

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


More information about the OpenStack-dev mailing list