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.
DescriptionVedashree Deshpande
2021-07-19 14:52:22 UTC
Description of problem:
Repositories in Satellite should be disabled by default.
Version-Release number of selected component (if applicable):
NA.
How reproducible:
- Create the first repo and sync, example EPEL_x86_64
http://mirrors.kernel.org/fedora-epel/6Server/x86_64/
- Create the next repo and sync, example EPEL_i386
2. Attach the subscription EPEL (Custom Product with 3 repos containing
different arch)
Actual results:
As soon as EPEL subscription is attached to a host, all repos (of different arch) are enabled by default.
Expected results:
Since Custom Product can now be created with multiple repos (which can be of different arch el5/6/7), at least disable them all when the Custom Product is attached, and let the user decide which one to enable from 'subscription-manager".
Additional info:
This is not good when the product is attached and all of them are enabled,
we will be seeing rhel7 repos enabled on a rhel6 host.
Current workaround is to create a Custom Product separately for each arch.
Customer needs this to be fixed after https://bugzilla.redhat.com/show_bug.cgi?id=1265120 closed as wontfix.
In Satellite 6.9, bug 1526564 introduced the ability to restrict a custom repository to a specific architecture and/or OS version.
Based upon the description above, it appears that this should address this particular situation.
If it doesn't and the desire is to support 'disable by default' for repositories, I'd recommend that we close this bugzilla as a dupe of bug 1265120. That bug has since been re-opened and it would be best to track all requests for via that single bugzilla.
Thanks!
(In reply to Brad Buckingham from comment #1)
> In Satellite 6.9, bug 1526564 introduced the ability to restrict a custom
> repository to a specific architecture and/or OS version.
>
> Based upon the description above, it appears that this should address this
> particular situation.
>
> If it doesn't and the desire is to support 'disable by default' for
> repositories, I'd recommend that we close this bugzilla as a dupe of bug
> 1265120. That bug has since been re-opened and it would be best to track
> all requests for via that single bugzilla.
>
> Thanks!
I agree. This feature was added *precisely* so that user doesn't have to create separate custom products per arch.
Description of problem: Repositories in Satellite should be disabled by default. Version-Release number of selected component (if applicable): NA. How reproducible: - Create the first repo and sync, example EPEL_x86_64 http://mirrors.kernel.org/fedora-epel/6Server/x86_64/ - Create the next repo and sync, example EPEL_i386 2. Attach the subscription EPEL (Custom Product with 3 repos containing different arch) Actual results: As soon as EPEL subscription is attached to a host, all repos (of different arch) are enabled by default. Expected results: Since Custom Product can now be created with multiple repos (which can be of different arch el5/6/7), at least disable them all when the Custom Product is attached, and let the user decide which one to enable from 'subscription-manager". Additional info: This is not good when the product is attached and all of them are enabled, we will be seeing rhel7 repos enabled on a rhel6 host. Current workaround is to create a Custom Product separately for each arch. Customer needs this to be fixed after https://bugzilla.redhat.com/show_bug.cgi?id=1265120 closed as wontfix.