Bug 1213225

Summary:	beaker-repo-update is too noisy, impossible to notice if an actual error occurs because of WARNINGs about junk OS major names
Product:	[Retired] Beaker	Reporter:	Dan Callaghan <dcallagh>
Component:	general	Assignee:	matt jia <mjia>
Status:	CLOSED CURRENTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	aigao, dcallagh, dowang, ebaak, mgrigull, mjia
Target Milestone:	21.0	Keywords:	Patch
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-26 06:17:17 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:

Description Dan Callaghan 2015-04-20 05:33:07 UTC

On a large Beaker installation that has been running for many years there is likely to be a lot of rubbish OS major names that do not really exist. As soon as an OS major has been created (even if the tree is later removed, or fixed to have a different OS major name) beaker-repo-update will try to fetch harness packages for it forevermore. The result is that running beaker-repo-update will produce a large number of WARNINGs like this:

2015-04-20 05:18:46,644 bkr.server.tools.repo_update WARNING Cannot retrieve repository metadata (repomd.xml) for repository: http:--download.lab.bos.redhat.com-beakerrepos-harness-help-. Please verify its path and try again

which make it very difficult to notice if there is an *actual* error (for example, when the upstream repos are missing a package that is supposed to be there).

The best option is probably to skip fetching packages for OS majors which have no existing trees. We could also consider turning these errors back into errors (rather than warnings) with a non-zero exit status.

Comment 1 Dan Callaghan 2015-04-20 05:33:39 UTC

*** Bug 1027517 has been marked as a duplicate of this bug. ***

Comment 2 matt jia 2015-05-19 06:44:02 UTC

On Gerrit:

 http://gerrit.beaker-project.org/#/c/4218/

Comment 5 Dan Callaghan 2015-08-26 06:17:17 UTC

Beaker 21.0 has been released.