<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Dec 12, 2016 at 4:47 PM, Barak Korren <span dir="ltr"><<a href="mailto:bkorren@redhat.com" target="_blank">bkorren@redhat.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You could've asked me, I explained exactly this on one of the threads<br>
that discuss these failures.<br>
Its not using the default configs though - just the none-proxies ones,<br>
those conf files are managed by us as well.<br></blockquote><div><br></div><div>That's exactly why I am writing this e-mail. So thanks for your reply and sorry for missing that mail thread.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Neah, its good to have around so we're resilient to proxy server failures.<br>
Since the check is based on the URL in the *-proxed.conf file, it<br>
means that when you change it to not use repoproxy, this check will<br>
not use it as well.<br></blockquote><div><br></div><div>I see. Maybe the best thing we can do is to remove metalink from non proxied configs and put there the same set of mirrors configuration we use in proxied, but just without proxy. This should remove that point of failure on Fedora side while keeping this mitigation for our proxy to be down.</div></div><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span><font color="#888888"><div>Anton Marchukov<br>Senior Software Engineer - <span><span><font color="#888888"><span><span><font color="#888888"><span><span><font color="#888888">RHEV CI - </font></span></span></font></span></span>Red Hat</font></span></span><br><br></div></font></span></div></div></div></div>
</div></div>