Bug 540140

Summary:	404's when downloading prestodelta.xml
Product:	[Fedora] Fedora	Reporter:	Jonathan Dieter <jonathan>
Component:	yum-presto	Assignee:	Jonathan Dieter <jonathan>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	james.antill, jonathan, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-12-11 08:03:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jonathan Dieter 2009-11-22 15:07:25 UTC

Some of our users are getting 404's when downloading prestodelta.xml.  I suspect it's because the users have an (outdated) cached copy of repomd.xml.  prestodelta.xml doesn't get downloaded until install time, which means it won't be in the cache.

Seth, how do you deal with this for filelists.sqlite and other.sqlite?  Is there any way for yum-presto to tell yum to invalidate the cache if it gets a 404?  Is that even a good idea?

Any suggestions?

Comment 1 seth vidal 2009-11-23 20:56:51 UTC

by the time presto data is grabbed it's a bit late to invalidate the metadata, I would think.

And I'm confused how the metadata is current enough for the pkgs to be downloaded but not for the presto data? it should be the same, I would think.

Comment 2 Jonathan Dieter 2009-11-24 05:18:05 UTC

(In reply to comment #1)
> by the time presto data is grabbed it's a bit late to invalidate the metadata,
> I would think.

Fair enough.

> And I'm confused how the metadata is current enough for the pkgs to be
> downloaded but not for the presto data? it should be the same, I would think.  

After a new push, most of the packages haven't changed, so the old metadata is mostly right.  For the few cases it's wrong that a user would notice (as far as I can see, it would have to be a package updated twice in two sequential pushes), you would get 404's for the missing packages.  prestodelta's name changes after *every* push, so you get a 404 every time you use the old metadata.

I do want to point out that I've only seen two people complaining about this on IRC, and a 'yum clean metadata' fixed it for them.  It may be that we're better off doing nothing here.

Comment 3 seth vidal 2009-11-24 19:46:12 UTC

I think it's odd that things are not timing out properly but unless it starts happening all over we should probably wait it out.

Comment 4 Jonathan Dieter 2009-12-11 08:03:34 UTC

Ok, going to close as WONTFIX; if we run into problems, we'll reopen.