此内容没有您所选择的语言版本。

1.3. Migrating from RHN Classic to RHSM


The Red Hat Network (RHN) Classic hosted subscription service on the Red Hat Customer Portal is being deprecated. The product life cycles for OpenShift Enterprise major versions 1 and 2 end before the RHN Classic end date. However, existing OpenShift Enterprise host systems that were registered using the RHN Classic hosted subscription method can be migrated to Red Hat Subscription Management (RHSM). This applies to systems running OpenShift Enterprise version 1 or 2 that host any OpenShift Enterprise component: broker, node, message server, database server, or combinations of these.
Red Hat recommends performing this migration on any affected systems as soon as possible. Once the transition to Red Hat Subscription Management for all Red Hat products is completed, then RHN Classic will no longer provide services to registered systems. More information on this transition can be found at https://access.redhat.com/rhn-to-rhsm.
The migration process unregisters the system from Red Hat Network (RHN) Classic, then registers it with Red Hat Subscription Management and attaches subscriptions using the subscription-manager CLI. The migration tools are contained in the subscription-manager-migration package. An additional package, subscription-manager-migration-data, is required to map the RHN Classic channels to Red Hat Subscription Management product certificates.
The Red Hat Subscription Management - Migrating from RHN Classic guide provides detailed instructions on migrating Red Hat Enterprise Linux systems to Red Hat Subscription Management.
The following procedure provides a basic overview of this migration and is catered to Red Hat Enterprise Linux systems hosting OpenShift Enterprise components.

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.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat