Bug 441129

Summary: RFE: Customizable maximum number of failures before canceling the metadata refresh
Product: [Fedora] Fedora Reporter: Stewart Adam <s.adam>
Component: PackageKitAssignee: Robin Norwood <robin.norwood>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhideCC: richard, 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: 2008-04-07 12:35:50 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 Stewart Adam 2008-04-06 15:41:14 UTC 
Description of problem:
See 441127 - PackageKit will keep re-downloading metadata until it gets the
right one like Yum does, however this can take lots of bandwidth and is
especially bad for users with bandwidth caps.

It would be great to have a "maximum # of failures" preference so that after X
failed downloads, it will just try again later.

Version-Release number of selected component (if applicable):
gnome-packagekit-0.1.11-1.fc9.x86_64

How reproducible:
Sometimes (depends on mirror syncs)

Steps to Reproduce:
1. Wait for PackageKit to refresh metadata
2. Observe bandwidth usage with a network monitor
  
Actual results:
Bandwidths will get high (800kbps) for a few seconds, drop to 0, then back up
again for several minutes as it tries another mirror.

Expected results:
Just an example, if the maximum failure count was 5 then after 5 bad mirrors it
would wait for them to sync (an hour or two?) then try again.
Comment 1 Richard Hughes 2008-04-07 09:16:53 UTC 
PackageKit doesn't know anything about mirrors, it lets yum handle all that. Do
you get the same behaviour with "yum clean all && yum check-updates"?
Comment 2 Stewart Adam 2008-04-07 12:35:50 UTC 
Oh, that would be why... Off to configure yum.conf! ;)