Bug 1108773

Summary: Cache not refreshed often enough
Product: [Fedora] Fedora Reporter: Ben Boeckel <fedora>
Component: dnfAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: akozumpl, fedora, packaging-team-maint, pnemade, rholy, tim.lauridsen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-24 05:39:48 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:
Attachments:
Description Flags
Shell log from a stale dnf cache none

Description Ben Boeckel 2014-06-12 14:24:54 UTC 
Description of problem:
When upgrading around once a week, dnf holds onto its cache and gets 404 errors on mirrors fairly regularly (I don't remember this happening with yum). Would it be possible to at least run a HEAD query on the repodata to see if it should be downloaded?

Version-Release number of selected component (if applicable):
dnf-0.5.2-1.fc20.noarch
Comment 1 Radek Holy 2014-06-13 10:50:43 UTC 
Hello, thank you for the report. We'll take a look.
Comment 2 Ales Kozumplik 2014-06-23 12:01:05 UTC 
Ben, can you please post a specific failure you've seen?
Comment 3 Ben Boeckel 2014-06-24 03:29:39 UTC 
Created attachment 911627 [details]
Shell log from a stale dnf cache

An attempt at installing perf after ~a week of not touching dnf. Note that there is no downloaded data for any remote repository and the repomd.xml is stating that it is newer than the cached files.
Comment 4 Ales Kozumplik 2014-06-24 05:39:48 UTC 
This is an issue with the fedora-rawhide-kernel-nodebug repo[1]: it is refreshed (supposedly) daily, but the metadata expire is left to the default 48 hours. Note that 24 hours is not enough in this case and the setting should be 0, i.e.:

metadata_expire = 0

Otherwise there is a always a chance the client will run into a just refreshed repo. Please contact the repo maintainer to do the appropriate fix. Thank you.

inb4 decrease the default.

[1] http://fedoraproject.org/wiki/RawhideKernelNodebug