Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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:
On the Web UI screen for entering activation key's the help text in the blue help bar gives an example of how to use the activation key. For example:
subscription-manager register --org="LAB" --activationkey="RHEL_Library" Where "LAB" is the organization name. It should be organization label.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create organization where org name is different from org label
2. Create activation key in this org
3. Subscribe system using the exact string from example in help bar (copy-paste)

Actual results:
Can't find orgnaization

Expected results:
subscribed

Additional info:

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

*** This bug has been marked as a duplicate of bug 1128245 ***