Hide Forgot
The following commands all behave differently when no options are provided: subscribe unsubscribe envrionments import repos for example subscribe shows: Error: This command requires that you specify a pool with --pool or use --auto. and repos shows: Error: This command requires that you specify a pool with --pool or use --auto. and unsubscibe actually shows the full text. Pick one model, and standardize across all the commands. Additionally, these commands: subscribe unsubscribe should check for registration before parsing the options.
Also, the redeem command.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Add config to this list too.
Checking for registration before the unsubscribe command does not work with offline setup. It was not put in. Config defaults to --list as before, it is the logical default. Error messages have been standardized. Commit 42e23b7bf6be4086d70b44a37dc41c5e987193b8 in master.
Testing with: subscription-manager-1.0.4-1.git.3.1768f90.el5 [root@jmolet-vm0 ~]# subscription-manager subscribe Error: This command requires that you specify a pool with --pool or use --auto. [root@jmolet-vm0 ~]# subscription-manager unsubscribe Error: This command requires that you specify one of --serial or --all. [root@jmolet-vm0 ~]# subscription-manager environments Error: This command requires that you specify an organizaiton with --org [root@jmolet-vm0 ~]# subscription-manager import Error: This command requires that you specify a certificate with --certificate. subscription-manager repos will now default to --list, see Bug 811594 . marking VERIFIED
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-0033.html