[openstack-dev] The recent gate performance and how it affects you

Davanum Srinivas davanum at gmail.com
Wed Nov 20 23:58:14 UTC 2013

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

-- 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
>>> queue.
>> 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?
>> Thanks,
>> Michael
> 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,
> Anita.
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Davanum Srinivas :: http://davanum.wordpress.com

More information about the OpenStack-dev mailing list