Bug 1669686 - dnf repo errors: "failovermethod" and "not found/reviving"
Summary: dnf repo errors: "failovermethod" and "not found/reviving"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-repos
Version: 29
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohan Boddu
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1710977 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-26 00:10 UTC by Grant
Modified: 2019-11-27 18:15 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 18:15:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Grant 2019-01-26 00:10:45 UTC
Description of problem: Running a "dnf update" since mid-November on Fedora 29 Workstation install has produced numerous errors and indicates it is using old/cached metadata to update packages.


Version-Release number of selected component (if applicable):
Both 4.0.9-1 and 4.0.9-2

How reproducible:
100%

Steps to Reproduce:
1. With this particular output in the actual results section, I have edited each repo file (/etc/yum.repos.d/X) to use the baseurl link rather than the metalink, in an attempt to fix things. However, the errors occur when the metalink is active (uncommented) and the baseurl is not active (commented).
2. Comment the metalnk= line in each repo file.
3. Uncomment the baseurl= line in the same repo file.
4. sudo dnf update



Actual results:

dnf does seem to update Fedora 29, however here is the output with many complaints:


Loaded plugins: builddep, config-manager, copr, debug, debuginfo-install, download, generate_completion_cache, needs-restarting, playground, repoclosure, repodiff, repograph, repomanage, reposync
DNF version: 4.0.9
cachedir: /var/cache/dnf
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-cisco-openh264.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
Fedora 29 openh264 (From Cisco) - x86_64        194  B/s | 543  B     00:02    
reviving: 'fedora-cisco-openh264' can be revived - repomd matches.
not found other for: Fedora 29 openh264 (From Cisco) - x86_64
not found modules for: Fedora 29 openh264 (From Cisco) - x86_64
not found updateinfo for: Fedora 29 openh264 (From Cisco) - x86_64
fedora-cisco-openh264: using metadata from Wed 12 Sep 2018 07:23:26 AM PDT.
Fedora Modular 29 - x86_64                       10 kB/s |  17 kB     00:01    
reviving: 'fedora-modular' can be revived - #metalink checksums match.
not found other for: Fedora Modular 29 - x86_64
not found deltainfo for: Fedora Modular 29 - x86_64
not found updateinfo for: Fedora Modular 29 - x86_64
fedora-modular: using metadata from Wed 24 Oct 2018 03:22:05 PM PDT.
Fedora Modular 29 - x86_64 - Updates             13 kB/s |  18 kB     00:01    
reviving: 'updates-modular' can be revived - #metalink checksums match.
not found other for: Fedora Modular 29 - x86_64 - Updates
not found deltainfo for: Fedora Modular 29 - x86_64 - Updates
updates-modular: using metadata from Wed 23 Jan 2019 06:09:48 PM PST.
Fedora 29 - x86_64 - Updates                     14 kB/s |  18 kB     00:01    
reviving: 'updates' can be revived - #metalink checksums match.
not found other for: Fedora 29 - x86_64 - Updates
not found modules for: Fedora 29 - x86_64 - Updates
updates: using metadata from Thu 24 Jan 2019 06:30:55 PM PST.
Fedora 29 - x86_64                               10 kB/s |  18 kB     00:01    
reviving: 'fedora' can be revived - #metalink checksums match.
not found other for: Fedora 29 - x86_64
not found modules for: Fedora 29 - x86_64
not found deltainfo for: Fedora 29 - x86_64
not found updateinfo for: Fedora 29 - x86_64
fedora: using metadata from Wed 24 Oct 2018 03:20:15 PM PDT.
RPM Fusion for Fedora 29 - Free - Updates       1.1 kB/s | 3.0 kB     00:02    
reviving: 'rpmfusion-free-updates' can be revived - #metalink checksums match.
not found other for: RPM Fusion for Fedora 29 - Free - Updates
not found modules for: RPM Fusion for Fedora 29 - Free - Updates
not found deltainfo for: RPM Fusion for Fedora 29 - Free - Updates
not found updateinfo for: RPM Fusion for Fedora 29 - Free - Updates
rpmfusion-free-updates: using metadata from Thu 24 Jan 2019 02:05:51 PM PST.
RPM Fusion for Fedora 29 - Free                 1.0 kB/s | 2.5 kB     00:02    
reviving: 'rpmfusion-free' can be revived - #metalink checksums match.
not found other for: RPM Fusion for Fedora 29 - Free
not found modules for: RPM Fusion for Fedora 29 - Free
not found deltainfo for: RPM Fusion for Fedora 29 - Free
not found updateinfo for: RPM Fusion for Fedora 29 - Free
rpmfusion-free: using metadata from Tue 23 Oct 2018 04:05:19 AM PDT.
RPM Fusion for Fedora 29 - Nonfree - Updates    4.5 kB/s |  13 kB     00:02    
reviving: 'rpmfusion-nonfree-updates' can be revived - #metalink checksums match.
not found other for: RPM Fusion for Fedora 29 - Nonfree - Updates
not found modules for: RPM Fusion for Fedora 29 - Nonfree - Updates
not found deltainfo for: RPM Fusion for Fedora 29 - Nonfree - Updates
not found updateinfo for: RPM Fusion for Fedora 29 - Nonfree - Updates
rpmfusion-nonfree-updates: using metadata from Thu 24 Jan 2019 02:22:23 PM PST.
RPM Fusion for Fedora 29 - Nonfree              5.7 kB/s |  14 kB     00:02    
reviving: 'rpmfusion-nonfree' can be revived - #metalink checksums match.
not found other for: RPM Fusion for Fedora 29 - Nonfree
not found modules for: RPM Fusion for Fedora 29 - Nonfree
not found deltainfo for: RPM Fusion for Fedora 29 - Nonfree
not found updateinfo for: RPM Fusion for Fedora 29 - Nonfree
rpmfusion-nonfree: using metadata from Tue 23 Oct 2018 04:34:17 AM PDT.
Completion plugin: Generating completion cache...
--> Starting dependency resolution
--> Finished dependency resolution
Dependencies resolved.
Nothing to do.
Complete!


Expected results:

dnf updates Fedora with no errors, at least with the default fedora repos.

Additional info:

Comment 1 Jaroslav Mracek 2019-05-11 19:52:03 UTC
"failovermethod=priority" is not supported by dnf. One of the possible solution would be to remove "failovermethod=priority" from repo files. Let's ask fedora-repos maintainers.

Comment 2 Kevin Fenzi 2019-05-11 21:52:34 UTC
This was already removed in rawhide and will appear in other releases when there's a need to update them. 

See https://src.fedoraproject.org/rpms/fedora-repos/c/52f903d59917f54596a258cfe7672148b84da82f?branch=master and https://bugzilla.redhat.com/show_bug.cgi?id=1653831

Do note that dnf does not show any of those messages by default. You must be running with -v or have changed the debuglevel?

Comment 3 Kevin Fenzi 2019-05-17 00:43:22 UTC
*** Bug 1710977 has been marked as a duplicate of this bug. ***

Comment 4 Federic 2019-10-22 11:40:01 UTC
Still getting tons of this stuff in Fed 29 a year later. Was this never attended to ?

BTW , not -v ; no additional debug level.




2019-10-22T10:49:56Z DDEBUG Extra commands: ['install', 'kernel-core']
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-cisco-openh264.repo; Configuration: OptionBinding with id "failovermethod" does not $
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-modular.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not$
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not$
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-modular.repo; Configuration: OptionBinding with id "failovermethod" does not$
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" $
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" $
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing-modular.repo; Configuration: OptionBinding with id "failovermethod" $
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not$
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not$
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates-testing.repo; Configuration: OptionBinding with id "failovermethod" does not$
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora-updates.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:56Z DEBUG Unknown configuration value: failovermethod=priority in /etc/yum.repos.d/fedora.repo; Configuration: OptionBinding with id "failovermethod" does not exist
2019-10-22T10:49:57Z DEBUG repo: using cache for: fedora-modular
2019-10-22T10:49:57Z DEBUG fedora-modular: using metadata from Wed 24 Oct 2018 23:22:05 BST.
2019-10-22T10:49:57Z DEBUG repo: using cache for: updates-modular
2019-10-22T10:49:57Z DEBUG updates-modular: using metadata from Fri 18 Oct 2019 02:23:48 BST.
2019-10-22T10:49:57Z DEBUG repo: using cache for: updates
2019-10-22T10:49:58Z DEBUG updates: using metadata from Mon 21 Oct 2019 00:12:37 BST.
2019-10-22T10:49:58Z DEBUG repo: using cache for: fedora
2019-10-22T10:49:59Z DEBUG fedora: using metadata from Wed 24 Oct 2018 23:20:15 BST.

Comment 5 Ben Cotton 2019-10-31 18:45:00 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.

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 29 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 Kevin Fenzi 2019-11-01 16:46:54 UTC
(In reply to Federic from comment #4)
> Still getting tons of this stuff in Fed 29 a year later. Was this never
> attended to ?
> 
> BTW , not -v ; no additional debug level.

It should definitely not be showing this without debug... are you sure you don't have something in /etc/dnf/dnf.conf?

Comment 7 Ben Cotton 2019-11-27 18:15:51 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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