Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The subscription-manager orgs output isn't very descriptive. Currently it only gives the key values of the orgs, and does not give the org displayNames (which is info needed to use orgs in the gui).
Version-Release number of selected component (if applicable):
subscription- manager-0.96.2-1.git.31.702703f.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. install subscription manager
2. run `subscription-manager orgs`
Actual results:
This output looks like debug print statements accidently left in the code:
[root@jmolet-vm0 ~]# subscription-manager orgs --username=testuser1
Password:
orgs:
snowwhite
admin
Expected results:
The output should have the same form as `subscription-manager list`
[root@jmolet-vm0 ~]# subscription-manager orgs --username=testuser1
Password:
+------------------------------+
testuser1 Organizations
+------------------------------+
OrgName: Snow White
OrgKey: snowwhite
OrgName: Admin User
OrgKey: admin
Additional info:
This will allow me to use this command to make the connection between my org key (used in the cli) and my org displayName (used in the gui). This is especially useful if my orgs look like this:
OrgName: Snow White
OrgKey: admin
OrgName: Juans Brown Sandwiches
OrgKey: snowwhite
Also, if there are no orgs available, it should simply look like this:
subscription-manager orgs --username=testuser3
Password:
testuser3 is not a member of any organizations.
Fixed in subscription-manager.git: e65faae2c8c895335ff2f4528566da19120a039b
Slight deviation for the no orgs situation, technically this case is listing orgs you can *register* to. We don't really have the notion of being a member of an org anymore, just roles/permissions, some of which may just be read-only, and those wouldn't appear here.
Sample output:
$ sudo env PYTHONPATH=src src/subscription-manager orgs --username=testuser1 --password=password
+-------------------------------------------+
testuser1 Organizations
+-------------------------------------------+
OrgName: Admin Owner
OrgKey: admin
OrgName: Snow White
OrgKey: snowwhite
$ sudo env PYTHONPATH=src src/subscription-manager orgs --username=testuser3 --password=password
testuser3 cannot register to any organizations.
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-2011-1695.html
Description of problem: The subscription-manager orgs output isn't very descriptive. Currently it only gives the key values of the orgs, and does not give the org displayNames (which is info needed to use orgs in the gui). Version-Release number of selected component (if applicable): subscription- manager-0.96.2-1.git.31.702703f.el6.x86_64 How reproducible: always Steps to Reproduce: 1. install subscription manager 2. run `subscription-manager orgs` Actual results: This output looks like debug print statements accidently left in the code: [root@jmolet-vm0 ~]# subscription-manager orgs --username=testuser1 Password: orgs: snowwhite admin Expected results: The output should have the same form as `subscription-manager list` [root@jmolet-vm0 ~]# subscription-manager orgs --username=testuser1 Password: +------------------------------+ testuser1 Organizations +------------------------------+ OrgName: Snow White OrgKey: snowwhite OrgName: Admin User OrgKey: admin Additional info: This will allow me to use this command to make the connection between my org key (used in the cli) and my org displayName (used in the gui). This is especially useful if my orgs look like this: OrgName: Snow White OrgKey: admin OrgName: Juans Brown Sandwiches OrgKey: snowwhite Also, if there are no orgs available, it should simply look like this: subscription-manager orgs --username=testuser3 Password: testuser3 is not a member of any organizations.