On Fri, Jul 20, 2018 at 10:45 AM Kamil Paral <kparal@xxxxxxxxxx> wrote:
On Fri, Jul 20, 2018 at 9:37 AM, Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:On 20.7.2018 06:25, Michal Novotny wrote:
Hello,
I am occasionally experiencing the following error in my day-to-day dnf use:
Failed to synchronize cache for repo 'fedora'
or
Failed to synchronize cache for repo 'updates'
I've had that happened even in local mock builds.
Do you also experience this error upon dnf operations like `dnf install` or `dnf refresh` or in local mock builds?
Happened to me yesterday. And immediate rerun "fixed" it. Maybe we can add some retrying to mock?We see this quite frequently in Taskotron, because we execute thousands jobs a day. I had to add "retry" keyword to all ansible tasks that use the dnf module. The reason is that MirrorManager sometimes returns an HTTP 5xx error (but when you try again, it works fine).It would help if DNF retried failed network requests (5xx codes), that's the best place to fix this for everybody. Anybody cares enough to file a bug and link it here?
I actually already filed the respective bugs:
There is even PR:
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.
clime
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/ZY4MPSHEIDSZHOFJGP7RPZRKOCLMGUY5/
