02387f06fe
Previously when moving code into elastic_recheck I had old pyc files lying around which tricked my computer into thinking things worked. In unit tests make sure to do 'from elastic_recheck' Change-Id: Ib6ddfd9ee1099e0047d94c0590392b5d3336a450
elastic-recheck
"Classify tempest-devstack failures using ElasticSearch"
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/elastic-recheck
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
- Move config files into a seperate directory
- Update sample config files
- Make unit tests robust
- Make pip installable, merge both binaries
- Add debug mode flag
- Split out queries repo
- Expand gating testing
- Cleanup and document code better
- Move away from polling ElasticSearch to discover if its ready or not
- Add nightly job to propose a patch to remove bug queries that return no hits -- Bug hasn't been seen in 2 weeks and must be closed
Main Dependencies
- gerritlib
- pyelasticsearch