Bug 980818 - fedup-cli --network 19: 404 Not Found
Summary: fedup-cli --network 19: 404 Not Found
Keywords:
Status: CLOSED DUPLICATE of bug 957364
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-03 09:59 UTC by bob mckay
Modified: 2013-10-09 19:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 19:58:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Transcript of fedup -d session (1.35 KB, text/plain)
2013-07-03 09:59 UTC, bob mckay
no flags Details
Yet another 404. Related? (1.60 KB, text/plain)
2013-07-03 15:13 UTC, Jim Wilson
no flags Details

Description bob mckay 2013-07-03 09:59:32 UTC
Created attachment 768168 [details]
Transcript of fedup -d session

Description of problem:
Network fedup fails to load boot image with 404 Not Found

How reproducible:
Always

Steps to Reproduce:
1. Update to latest version of F18 (July 3 2013)
2. fedup-cli --network 19

Actual results:
404 Not Found

Expected results:
Fedora upgrades to F19

Additional info:
Please see attached debug transcript

Comment 1 Jim Wilson 2013-07-03 15:13:48 UTC
Created attachment 768269 [details]
Yet another 404.  Related?

Last 20 lines of 5500-line fedup.log

Comment 2 Jim Wilson 2013-07-03 18:17:48 UTC
FWIW, 'fedup --clean' got rid of my Pinyin problem at the cost of redownloading the 400-or-so pacakges that preceded it.

I don't speak no steenkin' Pinyin, and I'm not sure why that package was installed anyway.  I have no clue why it wasn't found the first time or why --cleanup fixed the problem.

Comment 3 Will Woods 2013-07-03 21:53:31 UTC
You very likely just hit a mirror that wasn't fully populated yet.

If this problem continues after a week or so then I'll have another look.

Comment 4 bob mckay 2013-07-04 00:09:42 UTC
Hi Will; thanks for the explanation. If this is the case, then it's an expected issue that's likely to repeat. Maybe the curl call needs a test wrapped around it, with your explanation as text (i.e. something like "This failure probably resulted from a partially populated mirror. If you got this error early in a release cycle, please wait a few days and try again").

Comment 5 Will Woods 2013-10-09 19:58:04 UTC

*** This bug has been marked as a duplicate of bug 957364 ***


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