Bug 474850

Summary:	Multi Org Activation Keys prepend change
Product:	Red Hat Satellite 5	Reporter:	Clifford Perry <cperry>
Component:	Docs Reference Guide	Assignee:	John Ha <jha>
Status:	CLOSED CURRENTRELEASE	QA Contact:	wes hayutin <whayutin>
Severity:	medium	Docs Contact:
Priority:	low
Version:	510	CC:	adstrong, bperkins, msuchy
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	sat530	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-09-10 20:45:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	456984

Description Clifford Perry 2008-12-05 16:27:02 UTC

Description of problem:
With Satellite 5.1.0 we added code/feature for multiorg to prepend the org Id to the activation keys. This was mentioned in the multi org white paper. We should look to ensure this is within the main products documentation. In either a multiorg section and/or area's that we talk about activation key usage within the product. 

Cliff. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 John Ha 2009-02-26 06:53:14 UTC

Added in the latest (5.3.0) build of the Reference guide here:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.3.0/html/Reference_Guide/s1-multiorg-systems.html

Comment 3 wes hayutin 2009-05-21 15:22:14 UTC

verified 5/20

Comment 4 Miroslav Suchý 2009-08-21 11:51:59 UTC

verified in stage on xen5:

Activation keys have a new format since RHN Satellite 5.1.0, so the first few characters of the activation key are used to indicate which organization (by ID number) owns the activation.

I did not find mention of old format nowhere in doc

Comment 5 Brandon Perkins 2009-09-10 20:45:10 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1434.html