On 07/20/2018 11:15 PM, Miro Hrončok wrote:
> On 20.7.2018 19:56, Kevin Fenzi wrote:
>> On 07/20/2018 03:55 AM, Michal Novotny wrote:
>>
>>>
>>> I actually already filed the respective bugs:
>>>
>>>
https://bugzilla.redhat.com/show_bug.cgi?id=1591225
>>>
>>> There is even PR:
>>>
>>>
https://github.com/rpm-software-management/dnf/pull/1109
>>>
>>> that got blocked for an unknown reason and mainly unknown period.
>>>
>>> I wanted to confirm that more people are experiencing this issue,
>>> that it's
>>> not just some "local" network problem. The problem is that dnf does
not
>>> respect max_retries option for a repo when mirror manager is being
>>> contacted. I have no idea why it hasn't been fixed yet given that it
>>> affects basically all dnf users and it also quite significantly affects
>>> building in Copr.
>>
>> Thats a good workaround and we should do it, but I sure wish we could
>> track down when and why those sporadic 503's come from our mirrorlist
>> containers. ;(
>>
>> Perhaps we could add further debugging and track it down. I'll see what
>> I can do...
>
> Can we use something like Sentry?
https://sentry.io/
Thats a non free 3rd party service? no thanks. :)