RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

You can do a "yum install subscription-manager-migration" which will give you the rhn-migrate-classic-to-rhsm script to allow you to migrate RHN Classic to SAM/Subscriptions but it fails with the following error:

[root@some-host ~]# rhn-migrate-classic-to-rhsm 
Red Hat account: RHN-Account
Password: 

Retrieving existing RHN Classic subscription information ...

+-----------------------------------------------------+ 
System is currently subscribed to these RHN Classic Channels:
+-----------------------------------------------------+
rhel-x86_64-server-6
Unable to read mapping file: /usr/share/rhsm/product/RHEL-6/channel-cert-mapping.txt
[root@some-host ~]#

The subscription-manager-migration rpm package needs to depend on subscription-manager-migration-data so that the channel-cert-mapping.txt text file is there and the migration then succeeds.

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

The dependency is weird, but was set up on purpose so that subscription-manager could be included in Fedora at some point in the future. The migration-data rpm is RH internal, and thus cannot be a dependency for subscription-manager-migration (which is built from the same source rpm as subscription-manager). We provide instructions for how a user can create their own migration data certs and mapping, in case they ever wanted to use it.

*** This bug has been marked as a duplicate of bug 811779 ***