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 1634108 - [RFE] When creating a repo, add ability to specify disabled by default
Summary: [RFE] When creating a repo, add ability to specify disabled by default
Keywords:
Status: CLOSED DUPLICATE of bug 1265120
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.3.3
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-28 19:10 UTC by Dylan Gross
Modified: 2024-06-13 21:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-02 17:54:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3631251 0 None None None 2018-09-28 19:29:12 UTC

Description Dylan Gross 2018-09-28 19:10:51 UTC
1. Proposed title of this feature request

   [RFE] When creating a repo, add ability to specify disabled by default

3. What is the nature and description of the request?

   When a repo is created under a Product in Red Hat Satellite, if that product already exists, hosts will immediately see that content once the content view is promoted.

4. Why does the customer need this? (List the business requirements here)

   Customer has a large environment with many miscellaneous tiny repos under an umbrella Product.   They routinely add repos to this product.   While the Product is made available to wide variety of servers, each individual repo is not intended to be made available everywhere and creating many different products would be complex and difficult to manage.    Whereas if the repos were disabled by default at creation time, they could be selectively enabled where appropriate.

5. How would the customer like to achieve this? (List the functional requirements here)

   Add an option to set the default state of the repo (enabled / disabled) upon creation.   

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

   When creating a repo, it can be created as "Disabled" by default in a single action.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

   No

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

   No

9. Is the sales team involved in this request and do they have any additional input?

   No

10. List any affected packages or components.

   
11. Would the customer be able to assist in testing this functionality if implemented?

   Yes.

Comment 3 Sean O'Keeffe 2020-05-13 09:25:59 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.