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.
Bug 2018221 - [RFE] Improve the description of organization when registering with activation key
Summary: [RFE] Improve the description of organization when registering with activatio...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: subscription-manager-cockpit
Version: 9.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.1
Assignee: Jiri Hnidek
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-28 14:25 UTC by Kenny Tordeurs
Modified: 2022-11-15 13:17 UTC (History)
4 users (show)

Fixed In Version: subscription-manager-cockpit-2-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 11:21:22 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github candlepin subscription-manager pull 2997 0 None Merged 2018221: Cockpit: use "Organization ID" in label 2022-03-08 16:42:13 UTC
Red Hat Issue Tracker RHELPLAN-101330 0 None None None 2021-11-01 19:40:42 UTC
Red Hat Product Errata RHBA-2022:8366 0 None None None 2022-11-15 11:21:29 UTC

Description Kenny Tordeurs 2021-10-28 14:25:46 UTC
Description of problem:
When registering with Activation key it asks for Organization however it requires the Organization ID, it would be good to add some helper to the user to assist with the instructions on how to retrieve the organization id.

We could also rename the label to 'Organization ID' I believe that only when you register with activation key to Satellite you can use the organization name instead of the id and the main use case for this is to register against the Customer Portal.


Version-Release number of selected component (if applicable):
subscription-manager-1.28.13-4

How reproducible:
Register via subscription-manager gui with activation key

Comment 4 Zdenek Petracek 2022-04-20 12:33:40 UTC
Pre-verified on version:
[root@kvm-01-guest18 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 3.2.22-1
subscription management rules: 5.41
subscription-manager: 1.29.26-3.el9_0

As attachment shows, "Organization" changed to "Organization ID"
--> PASSED

Comment 10 errata-xmlrpc 2022-11-15 11:21:22 UTC
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 (subscription-manager-cockpit bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:8366


Note You need to log in before you can comment on or make changes to this bug.