Bug 707033 - Add information that migration from RHN Classic to Cert-based RHN is *not* supported
Summary: Add information that migration from RHN Classic to Cert-based RHN is *not* su...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Deployment_Guide
Version: 6.1
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: ---
Assignee: Deon Ballard
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel62 710223
TreeView+ depends on / blocked
 
Reported: 2011-05-23 19:36 UTC by Deon Ballard
Modified: 2011-12-06 15:41 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 15:41:09 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 726407 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 726407

Description Deon Ballard 2011-05-23 19:36:34 UTC 
Cf. http://post-office.corp.redhat.com/archives/tech-list/2011-May/msg00385.html

It needs to be explicitly stated in the documentation that there is no path to migrate a system from RHN Classic (channel-based) to Cert-bsed RHN (next gen entitlements).
Comment 8 Deon Ballard 2011-07-15 19:27:09 UTC 
This is in the 6.1 deployment guide:
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/entitlements.html#rhn-v-rhnclassic

And 6.1 release notes:
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Release_Notes/ar01s11.html

Similar text should be in the 5.7 deployment guide and release notes. I'll check and make sure those are properly added.
Comment 9 Andrew Ross 2011-07-28 22:18:19 UTC 
Verify content from comment#4 is in the docs.

Red_Hat_Enterprise_Linux-Deployment_Guide-6-en-US-1-132

Red_Hat_Enterprise_Linux-6.1_Release_Notes-6-en-US-0-42
Note You need to log in before you can comment on or make changes to this bug.