<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On 18 January 2017 at 00:41, Nadav Goldin <span dir="ltr"><<a href="mailto:ngoldin@redhat.com" target="_blank">ngoldin@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, as luckily this bug was discovered early, and mock cache refreshes<br>
once in 2 days, the only failure I could spot due to that is here[1],<br>
so to be sure Lago v0.32 won't get installed on the slaves, I cleaned<br>
up manually the mock cache on all ovirt-srv*, so on next run they<br>
should pull v0.33.<br></blockquote><div><br></div><div>To avoid having to play with mock caches in the future and remove the potential to break OST on Lago updates, I suggest we specify an exact lago version on the OST *.packages files. <br></div><div>This will allow using the OST check_patch job as essentially a gate for Lago updates. It will also mean that when we do updated Lago, mock caches will be invalidated immediately.<br></div></div><br><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Barak Korren<br><a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a><br>RHCE, RHCi, RHV-DevOps Team<br><a href="https://ifireball.wordpress.com/" target="_blank">https://ifireball.wordpress.com/</a></div>
</div></div>