Bug 1770619 - Log Error - Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Summary: Log Error - Unknown configuration value: failovermethod=priority in /etc/yum....
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-repos
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohan Boddu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-11 00:53 UTC by John Dodson
Modified: 2020-05-01 08:38 UTC (History)
16 users (show)

Fixed In Version: fedora-repos-30-3.fc30 and fedora-repos-31-2.fc31
Clone Of:
Environment:
Last Closed: 2020-05-01 08:38:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Dodson 2019-11-11 00:53:33 UTC
Description of problem:
Log Error - Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist

Version-Release number of selected component (if applicable):
dnf.noarch   4.2.11-2.fc30
fedora-repos-30-2.noarch

How reproducible:
Always

Steps to Reproduce:
1. dnf update
2. see logs (/var/log/dnf.log
3.

Actual results:
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist

Expected results:
No error

Additional info:
Obviously not fixed (yet) - when will it be in FC30?

Comment 1 John Dodson 2019-11-11 00:56:39 UTC
Should failovermethod=priority just be removed from /etc/yum.repos.d/fedora-updates-modular.repo?

Comment 2 Lukáš Hrázký 2019-11-11 12:31:41 UTC
Yes, the option should be removed from the config file. Seems it's still left in some distributed repo files, reassigning.

Comment 3 Paul Howarth 2020-03-08 13:02:03 UTC
Issue still present in fedora-repos-31-1 too.

Comment 4 Kevin Fenzi 2020-03-10 01:05:28 UTC
This is fixed in rawhide and f32...

I put in PRs to fix it for f30/f31, but they will only go out when there's a bigger need for an update.

Comment 5 Ben Cotton 2020-04-30 20:22:05 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Paul Howarth 2020-05-01 08:38:57 UTC
This was fixed in fedora-repos-30-3 and fedora-repos-31-2.


Note You need to log in before you can comment on or make changes to this bug.