Bug 956206

Summary:	Errata Applicability API - need repoids associated with each erratum
Product:	[Retired] Pulp	Reporter:	Brad Buckingham <bbuckingham>
Component:	consumers	Assignee:	Sayli Karmarkar <skarmark>
Status:	CLOSED NOTABUG	QA Contact:	Preethi Thomas <pthomas>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	2.1 Beta	CC:	cperry, mmccune, skarmark
Target Milestone:	---	Keywords:	Triaged
Target Release:	2.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-03 18:28:27 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:
Bug Depends On:
Bug Blocks:	950743

Description Brad Buckingham 2013-04-24 13:15:32 UTC

Description of problem:

In pulp v1, we used the following API to support a dashboard view of errata that need to be applied to consumers based upon a list of repoids provided:

https://fedorahosted.org/pulp/wiki/UGREST-Consumers#Listapplicableerrataforconsumersfromgivensetofrepositories

In pulp v2, the following API gives much of what is needed:
https://pulp-dev-guide.readthedocs.org/en/latest/rest-api/consumer/applicability.html

There is one small piece of needed information that is missing.  It is the repoids that each erratum exists in.  We use this information to correlate the repo to a product and then communicate that product back to the user.  This can help the user determine how important that errata may be to them.

Version-Release number of selected component (if applicable):
pulp-server-2.1.1-0.5.beta.el6.noarch

How reproducible:
always