Classify tempest-devstack failures using ElasticSearch
b0b024e080
We push each log file into ElasticSearch search separately, so knowing one file is there doesn't guarantee a different file from the same job is ready. So instead of checking for just console.html use facets to make sure all the relevant log files are ready. |
||
---|---|---|
tests | ||
.gitignore | ||
.testr.conf | ||
bot.py | ||
elasticRecheck.conf | ||
elasticRecheck.py | ||
LICENSE | ||
proof_of_concept.py | ||
queries.json | ||
README.md | ||
recheckwatchbot.yaml | ||
requirements.txt | ||
tox.ini |
elasticRecheck
Classify tempest-devstack failures using a list of elastic search queries.
Idea
When a tempest job failure is detected, by monitoring gerrit (using gerritlib), a collection of logstash queries will be run on the failed job to detect what the bug was.
Eventually this can be tied into the rechecker tool and launchpad
Future Work
- Pull in list of queries from a more flexible source, so a commit isn't needed to update each time
- Turn into a server app
- Make unit tests robust and not need internet
Dependencies
- gerritlib
- pyelasticsearch