Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop block that sets max mirror tries to 1 #2025

Closed
wants to merge 0 commits into from

Conversation

dcantrell
Copy link
Contributor

This functionality has always been present, but it's not clear why. It was never requested by any user. Removing these lines does allow everything to function as expected, but dnf makecache now retries when mirrors fail.

Resolves: RHEL-1342

@m-blaha
Copy link
Member

m-blaha commented Dec 6, 2023

FTR - it was introduced by commit d48bc7c as a fix for bug https://bugzilla.redhat.com/show_bug.cgi?id=922667

@jan-kolarik
Copy link
Member

jan-kolarik commented Dec 6, 2023

FTR - it was introduced by commit d48bc7c as a fix for bug https://bugzilla.redhat.com/show_bug.cgi?id=922667

Indeed, Marek, you're right. I've traced back through the history up to this PR, which appeared to introduce this functionality as the initial version, but I didn't notice the refactoring there 🙁

Now, it appears we have two somewhat conflicting requests. The older one suggests trying only the first mirror and skipping the others if it fails, while the new one proposes attempting a different one specifically in the case of a certificate problem. However, this distinction isn't recognized by librepo, which only has the LRO_MAXMIRRORTRIES option.

If we follow the suggestion in #1999 and remove the --timer parameter from the cron job, it will address the newer request related to certificate problems. Still, the older one won't be satisfied, and we will break the resource-awareness of the job, as reported in the past here. However, it's uncertain how relevant these problems are in the current context.

@jan-kolarik
Copy link
Member

@dcantrell Do you have any ideas how to proceed? Maybe we should bring this up for discussion during the subsystem meeting...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants