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.
Bug 1444156 - [RFE] Custom product repositories should be disabled by default to content host
Summary: [RFE] Custom product repositories should be disabled by default to content host
Keywords:
Status: CLOSED DUPLICATE of bug 1265120
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.2.8
Hardware: All
OS: All
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-20 17:58 UTC by Rajan Gupta
Modified: 2021-09-09 12:15 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-21 01:54:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Ian 2017-09-07 22:07:21 UTC 
In addition to being enabled on all hosts it also gets enabled in all the activation keys which should also, optionally, be disabled.
Comment 3 Chandni Sulekha 2018-01-31 07:20:35 UTC 
Description of RFE:

Customer would like to have the Custom product repositories should be disabled by default so that repository should not available to all the content host by default.


When adding a new repository to a content view and then publishing that content view to an environment, all hosts in that environment will automatically see the new repository and enable it.

Is it possible to prevent a new repository from being auto-enabled?

For eg.
The repository is an internal one labeled 'transient-ansible' inside of content view 'cv-transient-repos' which is part of composite content view 'Infrastructure Systems' that is associated with some hosts
Comment 5 jalviso 2018-05-21 01:54:58 UTC 

*** This bug has been marked as a duplicate of bug 1265120 ***
Note You need to log in before you can comment on or make changes to this bug.