- part of replacing puppet deployment with ansible and docker-compose
- current change tests container building
Change-Id: Id70f156e63751ebd14908cc5da969e964f63645b
Story: TRIPLEOCI-177
This automates the process to remove old queries
for fixed bugs. It's a bit conservative to start
so it doesn't check for open reviews nor does it
filter out affected projects with non-Fix* status
on the bug. It can be made more robust once we're
confident in how it works and play with it on the
open queries.
Change-Id: Iaaf17892804453b99a846be27457c88e5a8f8a55
This uses the ES health API to get the cluster health status
and pretty it up in our index/gate graph pages.
The cluster health API is documented here:
https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-health.html
Also add a note to the readme on how to view the openstack
ES cluster health.
Change-Id: I3df833cf5024af7282e2602e7dfa5db9c3384b6a
By default we add 'voting:1' to all queries so they are filtered
from the graph.
There are cases where we want to track bugs for non-voting jobs
in the graph, so add an 'allow-nonvoting' key for special bugs
that we want to track while we're trying to stabilize a job.
Updates the docs, adds a test query and unit test for the query
loader, fixes a bad query that was setting voting:1 already, and
removes the TODO in the query for bug 1539271.
Change-Id: I61b1d4b0faaa3f20fc5b04aa3392c68c61990866
Change I1f3c2a65104db39fdd7d786d421cded1b436a5f6 added the 'voting'
field which has been tracking results for a couple of weeks now, so
let's use it to filter the initial set of results for the uncategorized
bugs page.
Change-Id: If66c9f5f2f0dea344f941a6a072ff0c30a86e7f2
This is an upstreaming of:
https://github.com/dolph/spandexhttps://pypi.python.org/pypi/spandex
... which I'll nuke if this is merged.
I use this tool to write, test, and look for patterns in the results of
elastic recheck queries. I never use logstash.openstack.org anymore.
Change-Id: I864b22c05b398f6ad8ccb9009b5866f36b46789d
This is a non-voting job in the feature/pecan branch, so it's not
something that elastic-search will comment on in a change. However,
it's blowing up the uncategorized bugs page, so we can categorize
it here to cleanup that page.
Also add TODO for tracking voting flag in elasticsearch.
This comes up from time to time, so add a TODO that we need to track
whether or not a job is voting or not in elasticsearch, then we can use
that to filter out non-voting jobs from the uncategorized bugs page.
Related-Bug: #1496424
Change-Id: I820cce8e9a615732a5a81472fd40957db14ee2c9
This commit attempts to clearly state the current limitations with
using test_id filtering. Previously it wasn't entirely clear to some
people when you could use the test_id filtering because of the current
limitations in the subunit2sql data.
Change-Id: I580b45651283b0ffc851cc4369e883155fd5c5fd
This commit adds a new field to the query yaml test_ids which is a
list of test_ids that will be query the subunit2sql db to verify that
at least one of them failed on the failed uuid.
Change-Id: If3668709e3294b5d6bf9e1f082396fbc39c08512
Let's add more explicit instructions about removing bug signatures. This
came up in reviewing a new contributor change to do this which had quite
a bit of misunderstanding on how we do this.
Closes-Bug: #1477228
Change-Id: I81f33c05f1eefbbb61bd387fa86923da6bc588cf
From time to time we get a query change proposed that only hits on a
non-voting job and we have to explain why we don't accept those, so add
some wording to the readme about why non-voting jobs are skipped.
Example: I6e4c031b1f3a8ea8ec910bc70510971972d052d3
Change-Id: I9c3ce7cbfa6fe841c31f9f4b39ff75bea900b691
* Similar to suppress-graph
There are some gate failures that are expected and are real errors (such
as global-requirements mismatches in requirements jobs).
suppress-notifications allows us to classify these failures and remove
them from the unclassified page while not telling developers to recheck.
This can be used along with suppress-graph.
Change-Id: I6d905ba65e66e799a65598f8a5d5c3dd684feb8c
It's somewhat unclear what the "Unclassified failed jobs" in the
web UI actually represents, document this.
Change-Id: Ia4dafe1481ffa156ef20c48f41d0dc614ea7d2de
It is not clear what is referred to by 'filename query' when it is
recommended in place of a 'console query'. One might think it is the
query of the form filename:<filename>. But it is then recommended to use
the 'tags' field rather than the 'filename'.
This commit removes the ambiguity.
Related-Bug: #1368877
Change-Id: I980584bf3afba681321318aecffb566bfcf57e8b
We should mention something in the readme about the routine
process for deleting old queries and removing/rejecting
queries related to essentially incomplete bugs.
This has come up a few times in reviews so it's best to
document for expectations.
Change-Id: I2730f4947aa771704fb93fd824aac236d532527c
Currently the document reads as though wildcards are permissible
in certain situations. If wildcards are used in a query, the query
is likely to be rejected on that basis. This patch clarifies that
wildcards are not to be used in elastic search queries.
Change-Id: Ica400397f21963e78ae71c0efcc6bfdc2653ae53
Covers a few new things and expands on some existing notes
in further detail.
Co-authored-by: Sean Dague <sean@dague.net>
Change-Id: I9383783bf67411cebfaef6b82b5e08b3afe70afe
Change I3f093581 removed the resolved_at tag from the code but we missed
the readme, so update the readme here.
Change-Id: I0c9d8641a1005f042244f94c7e42ae5f72e0befd
We only index on INFO and higher log level messages and sometimes the
only good thing to fingerprint in the logs is at DEBUG level, but that
won't work with elastic-recheck right now, so we have to document the
limitation.
Change-Id: I89fc35bca9f99ffdb1a0a71d88d041ac2215dd9d
The logstash UI will return hits on wildcarded queries but the
ElasticSearch configuration by default disables wildcard analysis so
queries in elastic-recheck with wildcards currently do not work, so
let's make sure this is documented in the readme.
Related-Bug: #1266833
Change-Id: If6b9d99d7ba83272fc8b735ab9e67fe1ee993811
* Clarify what elastic-recheck does. Initially the primary goal was to
report back to gerrit, but we are using elastic-recheck for much more
then that now, so update docs to reflect that.
* Remove section on dependencies, it was used before we had a proper
requirements file.
* Remove references to adding the resolved_at option, as that is now
implemented
Change-Id: I6aa55bdf02174f13d86ad3309f5ad53110dc647d
Add a section to the README.rst that covers the process to add
bug signatures to elastic-recheck.
Change-Id: I93c830d8d2f414f5f52ae907e2a38a2a681c7534
Closes-bug: 1172387
... because it bothered me that it wasn't
also add in a few more relevant aspects to our current approach
to development, to keep this in line with how the project
actually works.
Change-Id: I6aa66263b3018d07512083cad86945295457ded1
this handles the piece of work we've been talking about for a while
in moving the queries.yaml file into a directory with a bunch of
files. These remain yaml so that they can be tagged with additional
metadata. This would support the concept of soft deleting as well
as other useful meta data to gauge our evolution of the bugs we
track over time.
This should see some real review as it's extensive enough of a
change that the existing tests might not be sufficient. However it
should be enough to move this forward quite a bit.
This also makes future looking statements about doing soft deletes
with a resolved_at keyword in the future. That implementation will
come later.
Change-Id: I86317fcf6f1886ab5b6c0ee154b29e71865c52b7
Now that people are contributing patches to queries.yaml, we should have
some docs on what we expect. This is a first pass at that.
Change-Id: Ib32ed2a8a24c3d70fe7bedfdf3820e895eed45cf
Make repo support 'tox -epep8' as we want this to be the first gating
check.
Don't make any actual code changes, just change setup and add files.
Further work is needed to re-organize the code, but that can be in a
separate patch.
Sorin Sbarnea