Bug 745156 - Subscription Manager migration tool
Summary: Subscription Manager migration tool
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: distribution
Version: 5.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 5.8
Assignee: RHEL Program Management
QA Contact: Ondrej Hudlicky
URL:
Whiteboard:
Depends On: 726407
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-11 14:22 UTC by William Poteat
Modified: 2011-10-27 13:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-11 19:12:35 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description William Poteat 2011-10-11 14:22:46 UTC
Description of problem:

Distribution bug for 726407

A new tool to migrate RHN Classic customers to the certificate-based RHN. 

RHEL5.6 and older had no product ids. A common upgrade using yum of RHEL5
system to RHEL5.7 or newer does not add product ids. When a
subscription-manager is installed on a system, it does not know about the
products currently installed. As a result, it cannot generate entitlement
certificates for the system.

Desired migration tool will do its best effort in guessing the products
currently installed on a system and will place productid(s) in
/etc/pki/product.

We have already determined that RHN Classic channels are not able to provide
productids since they are not sufficiently deterministic.

Comment 1 RHEL Program Management 2011-10-11 14:28:40 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 2 William Poteat 2011-10-11 19:12:35 UTC
This bug was unnecessary.


Note You need to log in before you can comment on or make changes to this bug.