Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
If, for whatever reason, multiple content sources contain the same errata, the errata shows up multiple times in the Promotions > Errata view

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Add RH provider; sync 6.1 standard and optional content 
2.  Promotions > Errata > All
3.  Look down the list; you'll probably readily see the dupes, but if not, click around until multiple lines end up highlighted.
  
Actual results:
We're gettind duplicate results, presumably because the same errata is used by multiple content sources

Expected results:
Uniquify the errata list

Additional info:
This also provides some evidence that we're not sorting these in some sort of predictable order, but not too concerned there, right now.

Created attachment 552461 [details]
screenshot

Need to rework how we show errata since the current way really isn't that usable. Errata can exist across version boundaries very easily.

For example, *every* errata that goes into RHEL 6.1Z stream will also end up in base RHEL6.

b4c296f83c307cf144eede7b08ec36287140ba61

This is part of a larger set of work done to add errata search to promotions.  This in turn should provide unique errata listings.

QA Verified.

getting rid of 6.0.0 version since that doesn't exist