Bug 2039906
Summary: | Invalid configuration value: failovermethod=priority in repo config files | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Suraj Raskar <sraskar> |
Component: | libdnf | Assignee: | Marek Blaha <mblaha> |
Status: | CLOSED ERRATA | QA Contact: | Eva Mrakova <emrakova> |
Severity: | unspecified | Docs Contact: | |
Priority: | low | ||
Version: | 8.5 | CC: | james.antill, mbanas, mblaha, naresh.sukhija_ext, nsella, sujagtap |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | Flags: | pm-rhel:
mirror+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libdnf-0.63.0-10.el8 | Doc Type: | No Doc Update |
Doc Text: |
If this bug requires documentation, please select an appropriate Doc Type value.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-08 10:47:13 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Suraj Raskar
2022-01-12 17:23:57 UTC
Hello, this is intentional, the option is not supported by dnf. You can remove it from all repo definitions in /etc/yum.repos.d/pgdg-redhat-all.repo and that'll get rid of the messages. We currently have the setting failovermethod=priority to support multiple yum servers, our dnf client configuration has this kind of lines: baseurl = http://server1/repo http://server2/repo Please suggest if after removing failovermethod=priority, any other option needs to be added or if dnf is intelligent enough to use the second server in case first server is unavailable PR that fixes the issue: https://github.com/rpm-software-management/libdnf/pull/1538 Test: https://github.com/rpm-software-management/ci-dnf-stack/pull/1126 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (libdnf bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:7711 |