1.3. Migrating from RHN Classic to RHSM

Procedure 1.1. To Migrate from RHN Classic to RHSM:

1. Use the oo-admin-yum-validator validation tool to verify that the system's yum configuration for the current subscription method is valid for the installed OpenShift Enterprise version and components. Use the -o option for the version and the -r option for the components.

   Example 1.1. Verifying a Host With the Validation Tool

   The following example is for an OpenShift Enterprise 2.2 broker host:

   # oo-admin-yum-validator -o 2.2 -r broker

   Copy to Clipboard Toggle word wrap
   If run without options, the validation tool attempts to detect the installed version and components. If any problems are reported, fix them manually or use the validation tool's --fix or --fix-all options to attempt to fix them automatically.
   Additional details on running the validation tool can be found in this knowledgebase article or in the oo-admin-yum-validator man page.
2. Install the migration tool packages:

   # yum install subscription-manager-migration subscription-manager-migration-data

   Copy to Clipboard Toggle word wrap
3. Use the rhn-migrate-classic-to-rhsm tool to initiate the migration. This tool has many options available, including registering to on-premise services and manually selecting subscriptions. If run without options, this tool migrates the system profile, registers the system with Red Hat Subscription Management, and automatically attaches the system to the best-matched subscriptions:

   # rhn-migrate-classic-to-rhsm

   Copy to Clipboard Toggle word wrap
   Consult the Red Hat Subscription Management - Migrating from RHN Classic guide or the rhn-migrate-classic-to-rhsm man page for details on additional options that may be relevant to your organization and environment.

   Note

   A known issue, which will be fixed in Red Hat Enterprise Linux 6.6, prevents the migration tool from automatically enabling the required channels on OpenShift Enterprise 2.1 systems. You can work around this issue by using the migration tool with the --force and --no-auto options; this continues registering the system to Red Hat Subscription Management, but does not automatically attach a subscription. Once the migration is complete, manually attach the desired OpenShift Enterprise subscription using the subscription-manager tool:

   # subscription-manager attach --pool Pool_ID

   Copy to Clipboard Toggle word wrap
4. After the migration completes, use the subscription-manager tool to list information about the migration including the previous system ID:

   Example 1.2. Listing Migration Information

   # subscription-manager facts --list | grep migr
   migration.classic_system_id: 09876
   migration.migrated_from: rhn_hosted_classic
   migration.migration_date: 2012-09-14T14:55:29.280519
   

   Copy to Clipboard Toggle word wrap
5. Use the oo-admin-yum-validator validation tool again to verify that the system's yum configuration is still valid under the new subscription method, and correct any issues that are reported.