Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

Description of problem:

After updating dnf package to its latest version, it starts complaining if any repo config file has "failovermethod=priority" parameter -

# rpm -qa | grep -i dnf
dnf-4.7.0-4.el8.noarch

Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/pgdg-redhat-all.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/pgdg-redhat-all.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/pgdg-redhat-all.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/pgdg-redhat-all.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/pgdg-redhat-all.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/pgdg-redhat-all.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Invalid configuration value: failovermethod=priority in /etc/yum.repos.d/pgdg-redhat-all.repo; Configuration: OptionBinding with id "failovermethod" does not exist

- Works fine with dnf-4.4.2-11.el8.noarch

- However this parameter is not being used in RH repos but wanted to verify if thats the bug.

Comment 2 Lukáš Hrázký 2022-01-17 14:26:10 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.

Comment 4 naresh.sukhija_ext 2022-01-17 14:35:20 UTC

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

Comment 11 Marek Blaha 2022-06-13 05:31:03 UTC

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

Comment 18 errata-xmlrpc 2022-11-08 10:47:13 UTC

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