I've just pushed up a change to puppet-elastic_recheck[1] to update the jobs
regex for elastic-recheck to start tracking tripleo.  What this means, is now
the elasticRecheck bot will start leaving comments on reviews once it matches a
failure in knows about.

The goal here is to better inform tripleo developers of the reasons of job
failures in an effort to find patterns / make fixes. From a developers POV, the
only difference you'll see if the elasticRecheck bot leaving a comment on your
patch when it finds a failure, if that does happen. Please take a moment to look
at the launchpad bug / logstash query.  

At the moment we are tracking:
  Bug 1708704 - yum client: [Errno 256] No more mirrors to try[2]

We have setup AFS mirrors to better help with yum failures, so I'd like to make
sure all jobs are properly setup to use it.


OpenStack Development Mailing List (not for usage questions)

Reply via email to