|Summary:||yum improper calculates percentage of overall work progress (more than 100%)|
|Product:||[Fedora] Fedora||Reporter:||JanS <jan.skowron>|
|Component:||yum||Assignee:||Seth Vidal <skvidal>|
|Status:||CLOSED CURRENTRELEASE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||9||CC:||ffesti, james.antill, katzj, pmatilai, tla|
|Fixed In Version:||python-urlgrabber-0:3.0.0-9||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-07-02 18:57:43 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description JanS 2008-07-02 17:49:15 UTC
Description of problem: While downloading rpm's yum displays download progress for file and overall downloads progress as percentage information. After something goes wrong (loss of network for a while), yum resumes downloading from another mirror. After this percentage overall progress is not well calculated. This could lead to value over 100% (as on attached screenshot) Version-Release number of selected component (if applicable): yum 3.2.16-2.fc9 Fedora 9, 18.104.22.168-55.fc9.x86_64 How reproducible: It is easy to reproduce. Try to update few bigger packeges and unplug ethernet in the middle of downloading process for a while (not too long not too short, few seconds to force yum to try another mirror) or disable wireless and plug ethernet after a while. Steps to Reproduce: 1. while yum is downloading rpm's, unplug your ethernet cable 2. after a while plug in, to force yum to try another mirror but continue to download 3. watch overall progress percentage (in brackets) 4. at the end you should see 101%, 102%, 103%, etc Actual results: 98%, 99%, 100%, 101%, 102%, 103%, 104%, etc... Expected results: 98%, 99%, 100%. Finished Additional info: see attachment
Comment 1 JanS 2008-07-02 17:49:15 UTC
Created attachment 310834 [details] yum screenshot with more than 100 percent overall progress
Comment 2 James Antill 2008-07-02 18:57:43 UTC
If you upgrade to the latest python-urlgrabber this should go away almost all the time (incl. the case in the screenshot). Although for all corner cases you need yum-3.2.17, when that comes out.
Comment 3 JanS 2008-07-02 19:52:08 UTC
Created attachment 310848 [details] same bug with newest python-urlgrabber 3.0.0-8.fc9 I have allready uptodate python-urlgrabber. And was able to reproduce ths bug once more (see attachment).
Comment 4 James Antill 2008-07-02 23:11:18 UTC
Can you show the top part of that output ... as I said there are certain conditions where urlgrabber can't fix it itself, for instance if the remote end doesn't give urlgrabber the full size ... or if it all gets downloaded but then doesn't checksum. Does it sound like any of that could have happened to you?
Comment 5 JanS 2008-07-03 14:10:06 UTC
Created attachment 310923 [details] yum output, last comunicate during download was (118%) see next attachement, screenshot from same situation as log, but caught in action 104%. I dont think that it is because of wrong full size got from internet, rather from interrupiton. One can check sizes of this updates and compare with the log. Maybe its because of one of my yum extensions? yum.noarch 3.2.16-2.fc9 installed yum-allowdowngrade.noarch 1.1.14-4.fc9 installed yum-fastestmirror.noarch 1.1.14-4.fc9 installed yum-metadata-parser.x86_64 1.1.2-8.fc9 installed yum-packagekit.x86_64 0.1.12-13.20080522.fc9 installed yum-presto.noarch 0.4.5-1.fc9 installed yum-utils.noarch 1.1.14-4.fc9 installed python-urlgrabber.noarch 3.0.0-8.fc9 installed
Comment 6 JanS 2008-07-03 14:12:38 UTC
Created attachment 310925 [details] screenshot during yum process from log given above
Comment 7 James Antill 2008-07-03 15:19:58 UTC
Ok, after being very confused for a bit, I see the problem. This was actually fixed in https://admin.fedoraproject.org/updates/F9/FEDORA-2008-5396 which is still in updates-testing ... sorry. I thought I'd already moved it to updates, so just took the version from there. I'll move it to updates now.