Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionKrist van Besien
2016-12-08 11:14:54 UTC
Description of problem:
The product content tab shows repositories that are not included in the content view associated with the registration key or host currently in focus.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Got to Hosts/Content Hosts
2. Select a host, look at the host details and select the "Product Content" tab
Actual results:
The Product Content tab shows all products, and when those are expanded all repositories are shown.
Expected results:
The Product Content tab shows only products and repositories associated to the content view this host is subscribed to.
Additional info:
The same behaviour is witnessed when modifying activation keys. This is inconvenient because when you want to change the repositories that are enabled when a host is subscribed using this key you have to go through a long list...