Bug 1125109 - Yum does not respect metadata_expire configuration option
Summary: Yum does not respect metadata_expire configuration option
Keywords:
Status: CLOSED DUPLICATE of bug 1104731
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum
Version: 6.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-31 04:42 UTC by BugMasta
Modified: 2014-08-20 16:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-20 16:35:26 UTC


Attachments (Terms of Use)

Description BugMasta 2014-07-31 04:42:30 UTC
Description of problem:
Yum seems to ignore metadata_expire option and insists upon re-downloading metadata even when it did so for another yum command just minutes ago.

Version-Release number of selected component (if applicable):
yum-3.2.29-43.el6_5.noarch

How reproducible:
Use yum. Become incredibly frustrated.

Steps to Reproduce:
1. check yum.conf and redhat.repo. Notice metadata_expire is set to 90m in yum.conf and 86400 in each repo definition in redhat.repo. 
2. yum -enablerepo=* list
2. wait while yum downloads metadata for all repositories
3. yum -enablerepo=* list
4. wait, with frustration growing, while yum downloads metadata for all repositories

Actual results:
Yum ignores metadata_expire and re-downloads metadata that was downloaded just minutes ago.

Expected results:
Yum does not download metadata again, until metadata_expire timeout set per-repo or in yum.conf is exceeded.

Additional info:
This is incredibly frustrating.

Comment 2 BugMasta 2014-08-20 07:27:18 UTC
Any chance of a response?
It would be nice to know if am I the only person seeing this issue, or if it is a known issue that no-one else seems to care about?

Comment 3 James Antill 2014-08-20 16:35:26 UTC
 You don't give quite enough enough to be 100% sure, but I'm pretty sure you are hitting BZ#1104731, where the rhsm plugin alters the redhat.repo file and thus. causes a refresh of all redhat repos. There are a few workarounds, and it should be getting fixed "soon", AIUI.

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


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