Bug 1428210
Summary: | yum retrieves metadata of the slow repository before detecting the fastest mirror by fastestmirror plugin | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Masahiro Matsuya <mmatsuya> |
Component: | yum-utils | Assignee: | Michal Domonkos <mdomonko> |
Status: | CLOSED ERRATA | QA Contact: | Eva Mrakova <emrakova> |
Severity: | medium | Docs Contact: | Lucie Vařáková <lmanasko> |
Priority: | medium | ||
Version: | 7.3 | CC: | emrakova, james.antill, jcastran, kwalker, mdomonko, ovasik, packaging-team-maint, richb, vmukhame |
Target Milestone: | rc | Keywords: | Patch, Regression |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | yum-utils-1.1.31-43.el7 | Doc Type: | Release Note |
Doc Text: |
The *fastestmirror* plug-in now orders mirrors before the metadata download
Previously, when the *yum* installer ran for the first time after a cache cleanup, the *fastestmirror* plug-in did not select the fastest mirror before metadata download. This sometimes caused a delay if some mirrors were slow or unavailable. With this update, the *fastestmirror* plug-in has been modified to have effect on mirror selection before metadata download. As a result, the mirrors are polled and arranged before metadata download, which prevents such delays.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-04-10 16:50:32 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1420851, 1465896, 1466368, 1473733 |
Description
Masahiro Matsuya
2017-03-02 02:11:50 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0919 |