Bug 441129 - RFE: Customizable maximum number of failures before canceling the metadata refresh
RFE: Customizable maximum number of failures before canceling the metadata re...
Product: Fedora
Classification: Fedora
Component: PackageKit (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Robin Norwood
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-06 11:41 EDT by Stewart Adam
Modified: 2008-04-07 08:35 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-07 08:35:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stewart Adam 2008-04-06 11:41:14 EDT
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):

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 05:16:53 EDT
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 08:35:50 EDT
Oh, that would be why... Off to configure yum.conf! ;)

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