Bug 847860

Summary: Registering a System using an Activation Key Fails
Product: Red Hat Satellite Reporter: Eric Helms <ehelms>
Component: Content ManagementAssignee: Eric Helms <ehelms>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: jrist, lzap, mmccune, vvaldez
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-15 16:41:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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