Bug 754872

Summary:	beaker-repo-update uses wrongly cached repodata when syncing from different repo urls
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	scheduler	Assignee:	Dan Callaghan <dcallagh>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.8	CC:	bpeck, dcallagh, mcsontos, rmancy, stl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-15 00:16:06 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.