Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Hi, This is even more motivation for us to revert the patch. Please consider this. Thanks Gary On 5/16/16, 6:23 PM, "Sean M. Collins" wrote: >Gary Kotton wrote: >> Hi, >> Actually the breakage is not sue to Q_L3_ENABLED. It is due to >>

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Gary Kotton wrote: > Hi, > Actually the breakage is not sue to Q_L3_ENABLED. It is due to > https://review.openstack.org/#q,d894221457efa3a2a0bf3db76a4c5e8ffba36e29,n, > z > The Q_L3_ENABLED is something that each CI can configure depending on what > their supported mode is. > Until now this mean

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Hi, Actually the breakage is not sue to Q_L3_ENABLED. It is due to https://review.openstack.org/#q,d894221457efa3a2a0bf3db76a4c5e8ffba36e29,n, z The Q_L3_ENABLED is something that each CI can configure depending on what their supported mode is. Until now this mean that L3 was supported by the

Re: [openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

I disagree. Sadly I approved the patch and it breaks all of the plugins that have L3 support but do not require an agent. Would it be possible that we unblock all of the plugins and try and work towards a better solution. The OVN example is good but that have a very small subset of tests. Thanks

[openstack-dev] [neutron][devstack] Third party CI breakage around Q_L3_ENABLED

Hi, During the neutron refactor of DevStack, I made a conscious decision to take the Q_L3_ENABLED variable and change the default from False to True. Most DevStack installations will want to have L3 services enabled, so my thinking was, let's make it the default. That broke some people last