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.

+++ This bug was initially created as a clone of Bug #1235849 +++

Description of problem:
For awhile, the Red Hat Customer Portal did not support creation of activation keys.  Hence the subscription-manager-gui and subscription-manager-firstboot were programmed to keep the "I will use an Activation Key" checkbox disabled whenever the "I will register with:" field contained a hostname matching the default subscription.rhn.redhat.com (or some redhat.com variant of this).  This restriction should now be removed.

Version-Release number of selected component (if applicable):
This applies to both RHEL6 and RHEL7 versions of
 subscription-manager-gui
 subscription-manager-firstboot



How reproducible:


Steps to Reproduce:
1. launch subscription-manager-gui and click register
2. click the Default button which should set the hostname field to "subscription.rhn.redhat.com"
3. try to register with a valid activation key

Actual results:
"I will use an Activation Key" checkbox is disabled

Expected results:
enabled


Additional info:
The workaround for this bug is to use the CLI version of subscription-manager to register with an activation key.

Created attachment 1079240 [details]
registering with activation key

Created an activation key via the account manager and proceeded to register a system with it in both the initial-setup and subman-gui.  Both succeeded.

Screenshots show using activation key with initial-setup

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://rhn.redhat.com/errata/RHBA-2015-2122.html