Bug 1395476

Summary:	Use PDC for repo relationship mapping for optional/add-on repositories
Product:	[Community] rpm-test-trigger	Reporter:	Tyrone Abdy <tabdy>
Component:	general	Assignee:	beaker-dev-list
Status:	MODIFIED ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unreleased	CC:	jorris
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:	1395499
Bug Blocks:

Description Tyrone Abdy 2016-11-16 01:25:37 UTC

Description of problem:

Currently we don't determine whether a relationship is an addon/optional/variant of another repository and should be included within the rpmdeplint run.

As an interim solution for initial deployment we will determine this using errata tool see related bug 1390801 for information on the work around solution for the relationship determination.

It appears that within PDC this information is stored to a degree, so it should be possible to use it to obtain this information.

Comment 2 Dan Callaghan 2016-11-16 02:58:06 UTC

So bug 1390801 is for the short term solution, and this is the "proper" solution to the same problem, right?

Comment 3 Tyrone Abdy 2016-11-16 03:36:20 UTC

Yeah bug 1390801 is the solution for turning on in our initial run of rpm-test-trigger with this being the longer term solution with proper integration to PDC to use that as our determining factor for the relationship of repositories in a release.

Comment 4 Tyrone Abdy 2017-01-09 00:35:18 UTC

https://gerrit.beaker-project.org/#/c/5560/