[Openstack] [neutron][devstack] Issue with Neutron L3 extension and flat provider network.

Michael Turek mjturek at linux.vnet.ibm.com
Wed Jun 8 15:41:52 UTC 2016


Should also mention that upon closer inspection 'Q_L3_ENABLED' isn't in 
use by devstack anymore. That being said, q-l3 is not in our list of 
enabled services.

On 06/08/2016 11:20 AM, Michael Turek wrote:
> We actually already explicitly in our localrc
>
> IP_VERSION=4
>
> Thanks for the suggestion though!
>
> On 06/08/2016 11:11 AM, Jens Rosenboom wrote:
>> 2016-06-08 16:49 GMT+02:00 Michael Turek <mjturek at linux.vnet.ibm.com>:
>>> Hey all,
>>>
>>> We have a CI setup that uses a single flat provider network.
>>>
>>> Originally devstack would create a network here
>>> (https://github.com/openstack-dev/devstack/blob/master/lib/neutron_plugins/services/l3#L144) 
>>>
>>> and we were good to go.
>>>
>>> However, recently we started also hitting this net-create
>>> (https://github.com/openstack-dev/devstack/blob/master/lib/neutron_plugins/services/l3#L201). 
>>>
>>> This fails as we do not have a tenant available for the second network.
>>> Specific error is 'Unable to create the network. No tenant network is
>>> available for allocation.'.
>>>
>>> This started happening after this merged
>>> https://review.openstack.org/#/c/318145
>>>
>>> Originally this second net-create wouldn't happen as we explicitly 
>>> disabled
>>> L3 via the Q_L3_ENABLED=False option. I'm wondering what the proper 
>>> way to
>>> skip this block of code now is. I'm guessing we need to disable the 
>>> router
>>> extension, but I'm not quite sure how to do that in devstack.
>>>
>>> Does anyone have any insight? Any help is appreciated, thanks!
>> Might be similar to what triggered
>> https://review.openstack.org/#/c/326638/ , so in that case you would
>> want to
>> change your setup to v4-only.
>>
>





More information about the Openstack mailing list