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 891625 - Firstboot:check "I will enable activation key" box ,enter the hosted url,takes you to register using activation key screen
Summary: Firstboot:check "I will enable activation key" box ,enter the hosted url,take...
Keywords:
Status: CLOSED DUPLICATE of bug 891621
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-03 13:04 UTC by Shwetha Kallesh
Modified: 2013-01-03 16:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-03 16:08:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Shwetha Kallesh 2013-01-03 13:04:22 UTC 
Description of problem:
Firstboot:check "I will enable activation key" box ,enter the hosted url,takes you to next register using activation key screen

Version-Release number of selected component (if applicable):
[root@rhel6 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: Unknown
subscription-manager: 1.8.0-1.git.97.83ecf19.el6
python-rhsm: 1.8.0-1.git.9.e5f5887.el6


How reproducible:


Steps to Reproduce:
1.Firstboot -r
2.Check "I will enable activation key" box
3.enter the hosted url
4.click next
  
Actual results:
 takes you to register using activation key screen

Expected results:


Additional info:
Comment 2 John Sefler 2013-01-03 14:41:37 UTC 
Here's what I believe is happening (applies to both firstboot and gui)...

1. before starting firstboot or subscription-manager-gui, the hostname within rhsm.conf is altered such that it does not match regex subscription\.rhn\.(\w*\.)*redhat\.com
2. firstboot or subscription-manager-gui is started and the "I will use an Activation Key" checkbox is enabled (because the hostname does not match the regex) and the user checks the box.
3. then the "I will register with:" hostname is changed to match the hosted regex subscription\.rhn\.(\w*\.)*redhat\.com which immediately disables the "I will use an Activation Key" checkbox.
4. despite the now disabled checkbox, it is already checked and the workflow continues to the activation key panel.


Request: To catch this situation, maybe an error dialog can be presented stating that the hosted sever does not honor activation keys.
  OR
Because the user does not have a valid activation key for hosted, they will have to go back and undo their steps in reverse order to re-enable the box and uncheck it.


Question: why is it necessary to disable the "I will use an Activation Key" checkbox at all?  Since the user will likely not have a valid activation key for a redhat hosted server, they will not have one to enter and have to navigate back (or they will enter a wrong key value and face the invalid credentials dialog).
Comment 3 Alex Wood 2013-01-03 16:08:09 UTC 
If you look in the wireframe link provided in the initial report of bug 817671, you'll see that Matt Reid requested that the activation key checkbox be disabled when users are using a hosted environment.  I think this makes sense since activation keys are not used in a hosted environment (as I understand it).

*** This bug has been marked as a duplicate of bug 891621 ***
Note You need to log in before you can comment on or make changes to this bug.