Bug 1983713

Summary: [RFE]Repositories should be disabled by default.
Product: Red Hat Satellite Reporter: Vedashree Deshpande <vdeshpan>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Cole Higgins <chiggins>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.9.0CC: ldelouw, rjerrido, thadzhie
Target Milestone: UnspecifiedKeywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-08 10:07:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vedashree 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.

Comment 1 Brad Buckingham 2021-10-15 15:40:31 UTC
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!

Comment 2 Rich Jerrido 2021-10-15 15:46:43 UTC
(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.

Comment 3 Rich Jerrido 2022-04-08 10:07:06 UTC

*** This bug has been marked as a duplicate of bug 1265120 ***

Comment 4 Red Hat Bugzilla 2023-09-15 01:11:42 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days