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.

In the Interface, navigate to: *Content > Errata > click on any Errata ID > Repositories tab*
In the filter bar Area (under "Repositories containing <erratum_id>") it says "There are no Content Views in this Environment" and the drop down filter for Content Views is greyed out.
This is true for every erratum I looked at and irrespective of the Lifecycle Environment that is selected.
When I check under Content Views, various versions of the views containing the relevant repositories are promoted to various Lifecycle Environments.

I have seen this affect both SUSE errata and CentOS errata on different Foreman/Katello installations. (Katello versions 3.4.5 and 3.5.1.1).

Created from redmine issue http://projects.theforeman.org/issues/23112

Upstream bug assigned to cfouant

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