Description of problem: Observe the confusion... [root@jsefler-6 ~]# subscription-manager orgs --username testuser1 --password password +-------------------------------------------+ testuser1 Organizations +-------------------------------------------+ Name: Admin Owner Key: admin Name: Snow White Key: snowwhite [root@jsefler-6 ~]# subscription-manager register --help | grep ORG --org=ORG register to one of multiple organizations for the user [root@jsefler-6 ~]# subscription-manager register --username testuser1 --password password --org "Admin Owner" Organization Admin Owner does not exist. ^^^^^^^^^^^^^^ WHAT? It exists in the report above! [root@jsefler-6 ~]# subscription-manager register --username testuser1 --password password --org "admin" The system has been registered with id: 573db0e1-b8c3-47aa-a71c-a625f249dbb2 ^^^ Ah! The description for --org should clarify that the org *key* should be specified. Version-Release number of selected component (if applicable): [root@jsefler-6 ~]# rpm -q subscription-manager subscription-manager-1.1.9-1.el6.x86_64 How reproducible: Steps to Reproduce: [root@jsefler-6 ~]# subscription-manager register --help | grep ORG Actual results: --org=ORG register to one of multiple organizations for the user Expected results: --org=ORG_KEY register to one of multiple organizations for the user by specifying the organization key ^^^^^^^ AND/OR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Would like agreement from mreid on this description
Also affects... [root@jsefler-6 ~]# subscription-manager environments --help | grep ORG --org=ORG specify organization for environment list but may be blocked by https://bugzilla.redhat.com/show_bug.cgi?id=875153#c2
Past string freeze, pushing.
How about: [root@jsefler-6 ~]# subscription-manager environments --help | grep ORG --org=ORG_NAME specify organization for environment list, using organization name [root@jsefler-6 ~]# subscription-manager register --help | grep ORG --org=ORG_KEY register to one of multiple organizations for the user, using organization key keeps things a little shorter by avoiding "by" and "using" over "specifying" saves a few characters as well. Thoughts?
https://github.com/candlepin/subscription-manager/pull/486
commit 017dae417368a2002b2b90fcc26773fd8736c654 Author: Bryan Kearney <bkearney> Date: Fri Jan 25 16:05:15 2013 -0500 878097: Clarify that the --org option is ORG_KEY and not ORG_NAME
Testing version... [root@jsefler-7 ~]# rpm -q subscription-manager subscription-manager-1.8.2-1.git.13.3fdfb73.el7.x86_64 [root@jsefler-7 ~]# subscription-manager register --help | grep ORG -A1 --org=ORG_KEY register to one of multiple organizations for the user, using organization key [root@jsefler-7 ~]# subscription-manager environments --help | grep ORG -A1 --org=ORG_KEY specify organization for environment list, using organization key [root@jsefler-7 ~]# subscription-manager service-level --help | grep ORG --org=ORG_KEY specify org for service level list [root@jsefler-7 ~]# For the sake of consistency, please update the org description under service-level to be... [root@jsefler-7 ~]# subscription-manager service-level --help | grep ORG --org=ORG_KEY specify organization when listing available service levels, using organization key
https://github.com/candlepin/subscription-manager/pull/511
commit a1a0ba588323a07e3355fe7b6cab82e8a4581b72 Author: Adrian Likins <alikins> Date: Fri Mar 1 10:21:35 2013 -0500 878097: update service-level org key help text
# rpm -qa | egrep "subscription-manager|python-rhsm" subscription-manager-firstboot-1.8.4-1.el7.x86_64 python-rhsm-1.8.7-1.el7.x86_64 subscription-manager-gui-1.8.4-1.el7.x86_64 subscription-manager-migration-1.8.4-1.el7.x86_64 subscription-manager-1.8.4-1.el7.x86_64 subscription-manager-debuginfo-1.8.4-1.el7.x86_64 # subscription-manager register --help | grep ORG --org=ORG_KEY register to one of multiple organizations for the # subscription-manager environments --help | grep ORG --org=ORG_KEY specify organization for environment list, using # subscription-manager service-level --help | grep ORG --org=ORG_KEY specify an organization when listing available service VERIFIED
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.
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-1332.html