[openstack-dev] The recent gate performance and how it affects you
anteaya at anteaya.info
Thu Nov 21 00:10:02 UTC 2013
On 11/20/2013 06:58 PM, Davanum Srinivas wrote:
> Anita, Joe,
> I need help with adding debug message in:
> to track down:
> Bug: https://bugs.launchpad.net/bugs/1251784 => message:"Connection to
> neutron failed: Maximum attempts reached" AND
> filename:"logs/screen-n-cpu.txt" Title: nova+neutron scheduling error:
> Connection to neutron failed: Maximum attempts reached
It has been decided on the bug report that 1251784 is a duplicate of
https://bugs.launchpad.net/nova/+bug/1251920 which has patch 57357 which
is in the gate.
I have no problem reviewing 56316 though.
> -- dims
> On Wed, Nov 20, 2013 at 5:43 PM, Anita Kuno <anteaya at anteaya.info> wrote:
>> On 11/20/2013 05:10 PM, Michael Still wrote:
>>> On Thu, Nov 21, 2013 at 7:44 AM, Clark Boylan <clark.boylan at gmail.com> wrote:
>>>> How do we avoid this in the future? Step one is reviewers that are
>>>> approving changes (or reverifying them) should keep an eye on the gate
>>> Talking on the -infra IRC channel just now, it has become clear to me
>>> that we need to stop approving _any_ change for now until we have the
>>> gate fixed. All we're doing at the moment is rechecking over and over
>>> because the gate is too unreliable to actually pass changes. This is
>>> making debugging the gate significantly harder.
>>> Could cores please refrain from approving code until the gate issues
>>> are resolved?
>> We are talking in -neutron and Mark McClain sent out an email to all
>> cores expressing this objective. He is also -2 any patch in check that
>> is not directly related to a gate blocking bug fix. Neutron is in
>> holding until we get the all clear from -infra.
>> Thanks Michael,
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev