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
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 ***