With zuul v3 lots of jobs have been renamed and the old "dsvm"
isn't really standard practice anymore, which means elastic recheck
skips processing for lots of failed jobs that would otherwise have
hits, including tempest-full and our grenade jobs.
This updates the regex to include devstack|tempest|grenade at
a minimum and leaves a TODO since there clearly lots of other
voting jobs which have categorized failures but aren't being processed.
Change-Id: I21e3d1058615321f84a00eab9d3dface7418fcc1
We've been tracking dsvm jobs for a long time, but also start
commenting for tripleo jobs. This is to help better classify job
failures.
Change-Id: I1e2369225c9bd83296684af0dd9ea0514d9098c4
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Elastic recheck commands pull the logstash url
from the provided configuration file. Allow this
url to be set.
Change-Id: I5fd2bc05f1cd6647fa43aaa307c47935c64b5f36
Depends-on: I282745796a40f10955e0c9893e817779b2d4d55a
Also, normalize some parameters to the status manifest to make it
more readable (since they follow the same pattern). And make the
ssh config for elastic-recheck bot match reviewday.
Change-Id: I2417f121e7b3685aab9540504cdd4c6db1754e67
moving elastic-recheck to a queries directory instead of a file
means we need to make the graphs support that. Also refactor out
the er_state_dir to make changing that easier when we pull in the
web console.
2Bupdate elastic-recheck bot config to use queries directory
Change-Id: Ifcc71511c066e8aee5cb74e013555c628f270e29
* modules/elastic_recheck/files/elastic-recheck.init: Minor
whitespace cleanup for space-before-tab indent on a comment line.
* modules/elastic_recheck/files/logging.config: New logging
configuration file for elastic-recheck IRC bot.
* modules/elastic_recheck/manifests/init.pp: Install the new logging
configuration file.
* modules/elastic_recheck/templates/elastic-recheck.conf.erb: Tell
the IRC bot to use the new logging configuration file.
Change-Id: I47cabb01df209c9f020846bcb272b9a2f796b0e5
This elastic recheck thing that classifies failures based on logstash
queries is awesome. We should run it on the OpenStack developer
infrastructure. Deploy it on logstash.o.o to keep related services
together.
Change-Id: I16ae7a32c2c48474454df17931779d0f60c3ed85
Matt Riedemann