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.
Description of problem:
We are using product Content Views to store RPM and Puppet modules together and freeze those per product release. The product Content Views are then bundled in Composite Content Views per hostgroup. The users shall only use the Composite Content Views.
Please add an option to Hide Content Views from host/hostgroup assignment boxes.
E.g. this can also be used to prepare a Content View without it being directly visible for all users.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Having this option to have a content view only for use by composite content views also can have a huge performance improvement.
- publishing the repo for consumers is not require anymore
- capsule synchronization is not required anymore for those content views
I am looking for feature where, if I have setup some filters in "roles", so when user is creating new hostgroup or modifying existing Host, he should only see contentviews with matching criteria in selection tab.
We have implemented a solution with using a separate Lifecycle environment for the compositecontentviews that shall be visible for the users. The library is then used for the building-block contentviews. The only downside is that we need to do 2 steps, a Publish and aPromote. To remvoe this inefficience there is a request to publuish directly to any lifeccle without the Library, see https://bugzilla.redhat.com/show_bug.cgi?id=1376474