Open Stack

On Thu, Aug 31, 2017 at 10:55:34AM +0200, Bogdan Dobrelya wrote:
> On 31.08.2017 10:33, Michele Baldessari wrote:
> > On Wed, Aug 30, 2017 at 11:31:14AM +0200, Bogdan Dobrelya wrote:
> >> On 30.08.2017 6:54, Emilien Macchi wrote:
> >>> On Tue, Aug 29, 2017 at 4:17 PM, Emilien Macchi <emilien at redhat.com> wrote:
> >>>> We are currently dealing with 4 issues and until they are fix, please
> >>>> do not approve any patch. We want to keep the gate clear to merge the
> >>>> fixes for the 4 problems first.
> >>>>
> >>>> 1) devstack-gate broke us because we use it as a library (bad)
> >>>> https://bugs.launchpad.net/tripleo/+bug/1713868
> >>>>
> >>>> 2) https://review.openstack.org/#/c/474578/ broke us and we're
> >>>> reverting it https://bugs.launchpad.net/tripleo/+bug/1713832
> >>>>
> >>>> 3) We shouldn't build images on multinode jobs
> >>>> https://bugs.launchpad.net/tripleo/+bug/1713167
> >>>>
> >>>> 4) We should use pip instead of git for delorean
> >>>> https://bugs.launchpad.net/tripleo/+bug/1708832
> >>>>
> >>>>
> >>>> Until further notice from Alex or myself, please do not approve any patch.
> >>>
> >>> The 4 problems have been mitigated.
> >>> You can now proceed to normal review.
> >>>
> >>> Please do not recheck a patch without an elastic-recheck comment, we
> >>> need to track all issues related to CI from now.
> >>> Paul Belanger has been doing extremely useful work to help us, now
> >>> let's use elastic-recheck more and stop blind rechecks.
> >>> All known issues are in http://status.openstack.org/elastic-recheck/
> >>> If one is missing, you're welcome to contribute by sending a patch to
> >>> elastic-recheck. Example with https://review.openstack.org/#/c/498954/
> >>
> >> That's a great example! Let me follow up on that and share my beginner's
> >> experience as well.
> >>
> >> Let's help with improving elastic-recheck queries to identify those
> >> unknown or new failures, this is really important. This also trains
> >> domain knowledge for particular areas, either openstack or *-infra, or
> >> tripleo specific.
> >>
> >> As beginners, we could start with watching for failing tripleo-ci
> >> periodic [0],[1] (available as RSS feeds) and gate jobs without e-r
> >> comments, also from that page [2].
> >>
> >> Then fetching the logs locally with tools like getthelogs [3], or
> >> looking into the logs.openstack.org directly, if advanced beginners wish so.
> >>
> >> Finally, identifying discovered (just do some grep, like I do with my
> >> tool [4]) errorish patterns and helping with root cause analysis. And,
> >> ideally, submitting new e-r queries (see also [5]) and corresponding lp
> >> bugs. And absolutely ideally, help with addressing those as well. This
> >> might be hard though as we may be not experts in some of the areas. Some
> >> of the error messages would literally mean nothing to us. For me, the
> >> most  But as the best effort, we could invite the right persons to
> >> look into that, or at least ask folks on #tripleo or #openstack-infra.
> >>
> >> [0]
> >> http://status.openstack.org/openstack-health/#/g/project/openstack-infra~2Ftripleo-ci
> >> [1]
> >> http://status.openstack.org/openstack-health/#/g/project/openstack~2Ftripleo-quickstart
> >> [2] http://status.openstack.org/elastic-recheck/data/others.html
> >> [3] https://review.openstack.org/#/c/492178/
> >> [4] https://github.com/bogdando/fuel-log-parse/blob/master/fuel-log-parse.sh
> >> [5]
> >> https://docs.openstack.org/infra/elastic-recheck/readme.html#running-queries-locally
> > 
> > Thanks Bogdan, this is very helpful. Do we have some docs/readme on [5].
> > It is failing here with a bunch of 404, so I presume I am missing a
> > proper elasticRecheck.conf file or some other settings?
> > 
> > I was basically trying to validate https://review.openstack.org/#/c/499516/ before
> > submitting it.
> 
> There is install docs [0] :)
> Although for my case, the following worked as well (given
> VENV=${HOME}/.virtualenvs):
> 
> $ mkvirtualenv erqtest
> $ pip install -r requirements.txt
> $ python setup.py develop
> $ ${VENV}/erqtest/bin/elastic-recheck-query queries/foo.yaml
> 
> [0] https://docs.openstack.org/infra/elastic-recheck/installation.html

:) I had gotten that far.

the usual python setup.py build + install in a new venv leaves me still with 404s all
over:
$ elastic-recheck-query queries/1713832.yaml 
2017-08-31 11:33:04  DEBUG    [urllib3.util.retry] Converted retries value: False -> Retry(total=False, connect=None, read=None, redirect=0)
2017-08-31 11:33:04  WARNING  [elasticsearch  ] GET /logstash-2017.08.31/_status [status:404 request:0.567s]
2017-08-31 11:33:04  DEBUG    [elasticsearch  ] > 
2017-08-31 11:33:04  DEBUG    [elasticsearch  ] < <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>404 Not Found</title> </head><body>
<h1>Not Found</h1> <p>The requested URL /logstash-2017.08.31/_status was not found on this server.</p> <hr>
<address>Apache/2.4.7 (Ubuntu) Server at logstash.openstack.org Port 80</address> </body></html>

Whereas the develop command fails me on:
Processing dependencies for elastic-recheck==0.0.1.dev2028
error: pbr 3.1.1 is installed but pbr<2.0,>=0.11 is required by set(['gerritlib'])

I'll investigate more when I'll have some time, I guess it is something
local to my setup if none else hits it.

Thanks,
Michele
-- 
Michele Baldessari            <michele at acksyn.org>
C2A5 9DA3 9961 4FFB E01B  D0BC DDD4 DCCB 7515 5C6D