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.
Bug 847860 - Registering a System using an Activation Key Fails
Summary: Registering a System using an Activation Key Fails
Keywords:
Status: CLOSED DUPLICATE of bug 848465
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Eric Helms
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-13 19:33 UTC by Eric Helms
Modified: 2013-08-16 17:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-15 16:41:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Eric Helms 2012-08-13 19:33:20 UTC 
Description of problem:
Attempting to register a system with an activation key fails due to the current user not being set properly.

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

How reproducible:
Always

Steps to Reproduce:
1. Create an Activation Key
2. Apply a subscription to the activation key
3. Using a client system properly configured, attempt to register using the activation key
  
Actual results:
Client system will receive an error: "Error updating system data, see /var/log/rhsm/rhsm.log for more details." 

And the /var/log/rhsm/rhsm.log will show: 
2012-08-13 14:40:19,793 [ERROR]  @cache.py:164 - Error updating system data
2012-08-13 14:40:19,793 [ERROR]  @cache.py:165 - Invalid credentials

Expected results:
The system should be registered appropriately or receive an error message that reflects the current state of the subscriptions attached to the Activation Key. 
For example, "Multi-entitlement not supported for pool with id"

Additional info:
This appears largely due to a chicken and egg problem whereby the current user is not properly set when attempting to look up activation keys when a client registers using an activation key.
Comment 4 Mike McCune 2012-08-15 16:41:43 UTC 

*** This bug has been marked as a duplicate of bug 848465 ***
Comment 6 Mike McCune 2013-08-16 17:57:05 UTC 
getting rid of 6.0.0 version since that doesn't exist
Note You need to log in before you can comment on or make changes to this bug.