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:

As a user, I want to see which errata is available in Library (or another lifecycle environment) that applies to my content host.

I've come across a few use cases for this.  The most common being:

- Security reporting - get an e-mail when there's a critical security fix that applies to my system.

- ITIL Change requests - some organizations may want to be able to generate a report of what will be applied during an update *before* the content is promoted to the production lifecycle environment

Created redmine issue http://projects.theforeman.org/issues/6577 from this bug

This was resolved as part of http://projects.theforeman.org/issues/7701 
http://projects.theforeman.org/issues/7702
http://projects.theforeman.org/issues/7703

The ability to view errata for a content host from the previous environment and library was added, arbitrary content views/environments are not supported

*** This bug has been marked as a duplicate of bug 588876 ***