Open Stack

Looking further in to this.  The bug you mentioned appears to have been
marked as a duplicate of a bug that was resolved about a month ago.  I
added the recheck comment to the gerrit review and Jenkins did not do
anything with it overnight.  I assume it noticed that the bug was marked
as resolved.

Further testing in devstack with this patch has gone well.  The patch
seems stable.  This patch is important for scaling the API servers as
Peter Feiner has pointed out a few times.  Can we get some eyes on this
Jenkins failure as I have yet to find anything to explain it.

Carl

From:  <Baldwin>, Carl Baldwin <carl.baldwin at hp.com>
Date:  Monday, September 9, 2013 6:05 PM
To:  OpenStack Development Mailing List <openstack-dev at lists.openstack.org>
Subject:  Re: [openstack-dev] [Neutron] Gate breakage for multi-process
API	patch.


Thank you for that information.  I see that rechecks page referenced from
the wiki now that you have mentioned it.  I have learned something.

Carl

Sent from my HTC

----- Reply message -----
From: "Davanum Srinivas" <davanum at gmail.com>
To: "OpenStack Development Mailing List"
<openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [Neutron] Gate breakage for multi-process API
patch.
Date: Mon, Sep 9, 2013 5:49 PM


Carl, 

if you check the "rechecks" page - http://status.openstack.org/rechecks/
you will see 18 other reviews hitting the same bug reported at
https://bugs.launchpad.net/tempest/+bug/1197476.

So, in your review for https://review.openstack.org/#/c/37131/, add a
comment "recheck bug 1197476" which will basically re-run the jenkins
tests and update the rechecks page with your review number.

See here for more info -
https://wiki.openstack.org/wiki/GerritJenkinsGit#Test_Failures

-- dims




On Mon, Sep 9, 2013 at 6:40 PM, Baldwin, Carl (HPCS Neutron)
<carl.baldwin at hp.com> wrote:

Hi all,

https://review.openstack.org/#/c/37131/

This review has been consistently marked as fail for the last three patch
sets.  I'm scratching my head over how the failure is related to the
patch.  Can anyone lend some insight?  Is this a known failure that is not
caused by my patch or is this failure actually due to my patch?

The test breaking is "test_008_check_public_network_connectivity."  I have
run the patch with the new api_workers config option set to 0, 1, 2, and 5
and I've been able to create instances that have full network connectivity
to my public network in each case.

Thanks,
Carl


_______________________________________________
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