Bug 1195003

Summary: Subscription-manager's manual does not document that wildcards are appropriate for the repo --{disable,enable} subcommand.
Product: Red Hat Enterprise Linux 6 Reporter: Rich Jerrido <rjerrido>
Component: subscription-managerAssignee: William Poteat <wpoteat>
Status: CLOSED CURRENTRELEASE QA Contact: John Sefler <jsefler>
Severity: low Docs Contact:
Priority: medium    
Version: 6.6CC: bcourt, dgoodwin, wpoteat
Target Milestone: rcKeywords: Reopened, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: subscription-manager-1.16.6-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-14 20:08:25 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:
Bug Depends On:    
Bug Blocks: 1209535    

Description Rich Jerrido 2015-02-21 22:02:14 UTC
Description of problem:
from man 8 subscription-manager :

REPOS OPTIONS
       The repos command lists all of the repositories that are available to a system. This command is only used for organizations which have a locally-hosted
       content service of some kind, like Subscription Asset Manager. With Red Hat’s hosted content service, there is only one central repository.


       --enable=REPO_ID
              Enables  the  specified  repository,  which  is made available by the content sources identified in the system subscriptions. To enable multiple
              repositories, use this argument multiple times.


       --disable=REPO_ID
              Disables the specified repository, which is made available by the content sources identified in the system subscriptions.  To  disable  multiple
              repositories, use this argument multiple times.


As a user, I can use either 

subscription-manager repos --enable='*' or subscription-manager repos --disable='*' to enable/disable all my repositories respectively. The manual does not document that wildcards are appropriate and it should. 

Version-Release number of selected component (if applicable):
subscription-manager-1.12.14-9.el6_6.x86_64


Additional info:

Comment 2 John Sefler 2015-02-23 15:36:53 UTC
Agreed....

The repos --help information indicates that wild cards are supported (and so should the man page)...

[root@jsefler-os6 ~]# subscription-manager repos --help | grep "REPOID" -A1
  --enable=REPOID       repository to enable (can be specified more than
                        once). Wildcards (* and ?) are supported.
  --disable=REPOID      repository to disable (can be specified more than
                        once). Wildcards (* and ?) are supported.


PS. Remember that "wildcard" is not a word.  See https://bugzilla.redhat.com/show_bug.cgi?id=1192120#c1

Comment 4 Mike McCune 2016-03-28 23:45:25 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 6 Jan Kurik 2017-12-06 10:31:53 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/