Bug 754872 - beaker-repo-update uses wrongly cached repodata when syncing from different repo urls
Summary: beaker-repo-update uses wrongly cached repodata when syncing from different r...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-18 00:52 UTC by Dan Callaghan
Modified: 2019-05-22 13:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-15 00:16:06 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Dan Callaghan 2011-11-18 00:52:02 UTC 
If beaker-repo-update is run pointing at multiple different base URLs whose contents are not identical, it could use inconsistent cached repodata and become confused.

One symptom is package checksum failures where there should be none:

failure: ../../rpms/rhts-test-env-4.43-1.fc14.noarch.rpm from beaker-repo-update-harness-Fedora16: [Errno 256] No more mirrors to try.

The cause is that the yum repodata caches are keyed on repo id (in this case, beaker-repo-update-harness-Fedora16) and this does not change even when a different base URL is used. Yum will therefore use the existing cache which might contain different repodata.
Comment 1 Dan Callaghan 2011-11-18 00:52:40 UTC 
A workaround is to remove yum's cache in /var/tmp/yum-root-* before running beaker-repo-update.
Comment 2 Dan Callaghan 2011-11-18 01:16:55 UTC 
Probably the easiest way to avoid the incorrect cache reuse is to base the repoids on the repo url.
Note You need to log in before you can comment on or make changes to this bug.