Re: [openstack-dev] [neutron] Gate-failure bugs spring cleaning

On 21/04/2018 14:16, Slawomir Kaplonski wrote: > Hi Neutrinos, > > There is time for some spring cleaning now so I went through list of Neutron > bugs with „gate-failure” tag https://tinyurl.com/y826rccx > I mark some of them as incomplete if there was not hits of same errors in > last 30

Re: [openstack-dev] [Neutron] Gate failure

On 26 February 2016 at 11:43, Doug Wiegley wrote: > This has merged, so you can resume your previously scheduled > mad-merge-for-Mitaka and break it all again. > Assume this is the default behavior unless told otherwise. So, yes go nuts! Cheers, Armando > >

Re: [openstack-dev] [Neutron] Gate failure

This has merged, so you can resume your previously scheduled mad-merge-for-Mitaka and break it all again. Thanks, doug > On Feb 25, 2016, at 2:46 PM, Armando M. wrote: > > Folks, > > The API job recent breakage prevents us from merging code. Please refrain > from pushing

Re: [openstack-dev] [Neutron] Gate failure

UPD both fixes merged, should now be safe to recheck neutron patches. Doug Wiegley wrote: This fix failed to merge, due to a new regression in how another job is using dib. Here's a non voting patch for that, until it gets debugged:

Re: [openstack-dev] [Neutron] Gate failure

This fix failed to merge, due to a new regression in how another job is using dib. Here's a non voting patch for that, until it gets debugged: https://review.openstack.org/267223 The fail stack is now two deep. Doug > On Jan 13, 2016, at 11:41 AM, Armando M. wrote: > >

Re: [openstack-dev] [Neutron] Gate failure

Ugh, this test is racey. I should have paid closer attention before I +2'ed, my bad. It just iterates external ports and uses an IP not in that list so if another test grabbed the same IP, the floating IP creation request specifying that IP will fail. Revert proposed here:

Re: [openstack-dev] [Neutron] Gate failure

On Wed, Jan 6, 2016, at 08:48 PM, Henry Gessau wrote: > Armando M. wrote: > > Hi folks, > > > > Due to [1], Neutron related jobs (api, and lbaas) are failing. Please hold > > your +A button until the issue is resolved. > > > > Thanks, > > Armando > > > > [1]

Re: [openstack-dev] [Neutron] Gate failure

Ah, that was a bit misleading. We're not leaking any floating IPs. The create method for them adds them to a list that is cleaned up on teardown. The issue was that the get_unused_ip method was iterating over v4 and v6 subnets. So if it happened to pick a v6 subnet, it would cause the test to

Re: [openstack-dev] [Neutron] Gate failure with grenade

On 14 December 2015 at 10:18, Paul Michali wrote: > Thanks Sean! > > On Mon, Dec 14, 2015 at 12:58 PM Armando M. wrote: > >> On 14 December 2015 at 09:51, Sean Dague wrote: >> >>> On 12/14/2015 12:32 PM, Armando M. wrote: >>> > Hi folks, >>>

Re: [openstack-dev] [Neutron] Gate failure with grenade

On 14 December 2015 at 09:51, Sean Dague wrote: > On 12/14/2015 12:32 PM, Armando M. wrote: > > Hi folks, > > > > Something snuck in past the gate last night [1]. Please stop rechecking > > and pushing in the merge queue until the matter is resolved. > > > > I will follow up with

Re: [openstack-dev] [Neutron] Gate failure with grenade

On 12/14/2015 12:32 PM, Armando M. wrote: > Hi folks, > > Something snuck in past the gate last night [1]. Please stop rechecking > and pushing in the merge queue until the matter is resolved. > > I will follow up with details, if someone knows more, please find me on IRC. > > Thanks, > Armando

Re: [openstack-dev] [Neutron] Gate failure with grenade

Thanks Sean! On Mon, Dec 14, 2015 at 12:58 PM Armando M. wrote: > On 14 December 2015 at 09:51, Sean Dague wrote: > >> On 12/14/2015 12:32 PM, Armando M. wrote: >> > Hi folks, >> > >> > Something snuck in past the gate last night [1]. Please stop rechecking