Bug 846207
| Summary: | multiple specifications of --enable doesnot throw error when repo id is invalid | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Shwetha Kallesh <skallesh> |
| Component: | subscription-manager | Assignee: | Alex Wood <awood> |
| Status: | CLOSED ERRATA | QA Contact: | Entitlement Bugs <entitlement-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3 | CC: | alikins, awood, bkearney, jmolet, jsefler, spandey |
| Target Milestone: | rc | ||
| Target Release: | 6.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | subscription-manager-1.1.2-1 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 08:55:33 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: | 771481 | ||
|
Description
Shwetha Kallesh
2012-08-07 06:51:58 UTC
In my opinion, I like the valid repos to be enabled/disabled and NOT error out when an invalid repo is encountered. This is the current behavior. HOWEVER, the absence of feedback for invalid repos could be improved. For example: [root@jsefler-rhel59 ~]# subscription-manager repos --list | grep "Repo Id" Repo Id: content-label-empty-gpg Repo Id: never-enabled-content Repo Id: content-label-no-gpg Repo Id: always-enabled-content Repo Id: content-label [root@jsefler-rhel59 ~]# subscription-manager repos --enable=content-label-no-gpg --enable=always-enabled-content --enable=FOO --enable=content-label --disable=content-label-empty-gpg --disable=BAR --disable=content-label Repo content-label-no-gpg is enabled for this system. Repo always-enabled-content is enabled for this system. Repo content-label is enabled for this system. Repo content-label-empty-gpg is disabled for this system. Repo content-label is disabled for this system. [root@jsefler-rhel59 ~]# Actual Results: above^ Expected Results: [root@jsefler-rhel59 ~]# subscription-manager repos --enable=content-label-no-gpg --enable=always-enabled-content --enable=FOO --enable=content-label --disable=content-label-empty-gpg --disable=BAR --disable=content-label Repo content-label-no-gpg is enabled for this system. Repo always-enabled-content is enabled for this system. Repo FOO is not entitled on this system. <==================== IMPROVEMENT Repo content-label is enabled for this system. Repo content-label-empty-gpg is disabled for this system. Repo BAR is not entitled on this system. <==================== IMPROVEMENT Repo content-label is disabled for this system. commit 174e56ee350584c88289a5188d44809dda6b46a3 Available in subscription-manager-1.1.2-1+ Verified!! [root@rhel-64-server ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.7.17-1 subscription-manager: 1.1.5-1.el6 python-rhsm: 1.1.4-1.el6 [root@rhel-64-server ~]# subscription-manager repos --list | grep "Repo Id" Repo Id: awesomeos Repo Id: awesomeos-x86_64 Repo Id: awesomeos-modifier Repo Id: awesomeos-ppc Repo Id: always-enabled-content Repo Id: never-enabled-content Repo Id: content-label-empty-gpg Repo Id: awesomeos-s390x Repo Id: content-label-no-gpg Repo Id: awesomeos-ia64 Repo Id: awesomeos-ppc64 Repo Id: awesomeos-i686 Repo Id: content-label [root@rhel-64-server ~]# subscription-manager repos --enable=content-label-no-gpg --enable=always-enabled-content --enable=FOO --enable=content-label --disable=content-label-empty-gpg --disable=BAR --disable=content-label Error: FOO is not a valid repo id. Use --list option to see valid repos. Repo content-label-no-gpg is enabled for this system. Repo always-enabled-content is enabled for this system. Repo content-label is enabled for this system. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0350.html |