Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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: WebUI for
example.com/activation_keys/:id/info
suggest using
subscription-manager register --org="<org_name>" --activationkey="<activation_key>"
instead of
subscription-manager register --org="<org_label>" --activationkey="<activation_key>"
Version-Release number of selected component (if applicable):
sat6-Satellite-6.0.4-RHEL-6-20140730.0-Satellite-x86_64-dvd1.iso
How reproducible: always/deteminitic
Steps to Reproduce:
1. create organization with spaces in name
2. create AK for this org
3. observe suggested registration command
Actual results:
use name (spaces)
Expected results:
use label (underscores)
Additional info:
It does not work with name instead of label...
Comment 1RHEL Program Management
2014-08-08 17:03:49 UTC
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.
Moving to POST since upstream bug http://projects.theforeman.org/issues/7278 has been closed
-------------
Christine Fouant
Applied in changeset commit:katello|144b8ad4db94f649c5360fde95021ff9b6b0cdea.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds ***
Version Tested:
RHEL66 / RHEL7
katello-2.1.0-1.201411061509gitb0b8f43.el7.noarch
katello-repos-2.1.1-1.el7.noarch
katello-installer-2.1.0-1.201411172212git9d6f424.el7.noarch
rubygem-hammer_cli_katello-0.0.6-1.201411202238git7fa4778.git.0.a5a9308.el7.noarch
ruby193-rubygem-katello-2.1.0-1.201411202218git791c8dd.el7.noarch
katello-server-ca-1.0-1.noarch
katello-certs-tools-2.0.1-1.el7.noarch
pulp-katello-0.3-3.el7.noarch
katello-default-ca-1.0-1.noarch
subscription-manager-1.1.23-1.el6.x86_64
*** This bug is verified in upstream. This fix should eventually land in future downstream builds ***
Version Tested:
RHEL66 / RHEL 7
katello-installer-2.1.0-1.201412071742git114a910.el6.noarch
pulp-katello-0.3-3.el6.noarch
katello-default-ca-1.0-1.noarch
katello-repos-2.1.1-1.el6.noarch
ruby193-rubygem-katello-2.1.0-1.201412101236git4521c2f.el6.noarch
katello-certs-tools-2.0.1-1.el6.noarch
katello-server-ca-1.0-1.noarch
rubygem-hammer_cli_katello-0.0.6-1.201412101306git7d5e313.git.0.44a4586.el6.noarch
katello-2.1.0-1.201411061509gitb0b8f43.el6.noarch
katello-ca-consumer-qe-foreman-rhel66.usersys.redhat.com-1.0-1.noarch
Verified against four Satellite 6.0.8 applications, two of which are running on RHEL 6.6 and the other two of which are running on RHEL 7.0. Here was my verification procedure:
1. Create an organization named "before & after".
2. Switch to that organization's context.
3. Create an activation key named "activation & key".
Here is the message advertised on each machine after the above steps:
This activation key may be used during system registration. For example:
subscription-manager register --org="before___after" --activationkey="activation & key"
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.
https://access.redhat.com/errata/RHBA-2015:0247