Description

RedHat Update Infrastructure (version 2) has been discontinued by RedHat and a new MCP RHUI architecture has been created using RHUI version 3.  Due to the differences between architectures, it was necessary to develop a migration process to move client VMs from the old architecture to the new architecture.  This document describes what to expect during the migration process.

The process of moving customer VMs from RHUI v2 to RHUI v3 is initiated via a standard 'yum update' command.  Once launched, the process is fully automated and no user interaction is required; however, users should be aware of what to expect during the migration process.

Important Note

The update process can be initiated via a general 'yum update'; however, to ensure a successful migration to the new architecture, updating only the MCP client is highly recommended. 

Content / Solution:

  1. Check the existing MCP client version (this example shows the "rhel7" version of the MCP client)

    # rpm -qa mcp-client-rhel7
    mcp-client-rhel7-2.0-1
  2. To initiate the migration process, simply instruct YUM to update the MCP Client (replace "rhel7" with the version of the RedHat server being migrated.  i.e. "rhel5", "rhel6" or "rhel7").  This will initiate the YUM update process and install an intermediate MCP client RPM.  This intermediate RPM will install the proper MCP Client RPM based on the GEO and RHEL version running on the VM. The new client RPM contains everything necessary for the customer VM to start using the new RedHat Update Infrastructure.

     # yum update -y mcp-client-rhel7    :
        :
    +--------------------------------------------------------------+
    |   Starting RHUI Client installation.                         |
    |   Please see /var/log/rhui-client-install for details        |
    +--------------------------------------------------------------+
  3. The upgrade runs as a detached process and will take approximately 5 minutes to complete.  During this time, no terminal output will be displayed; however, the progress can be monitored by running "tail" in follow-mode on the log file:

     # tail -f /var/log/rhui-client-install[02/05/19 18:35:44] Starting RHUI Client Installation.
    [02/05/19 18:35:44]     Distro: rhel7
    [02/05/19 18:35:44]     URL: http://clientcfg.na.rhui.mcp-services.net:34324/getClientCfg/rhel7
    [02/05/19 18:35:45]     Client RPM: mcp-client-rhel7-3.1-1.noarch.rpm
    [02/05/19 18:35:45]     YUM is not locked.  Continuing install...
    [02/05/19 18:35:46]     Removing old MCP client...(mcp-client-rhel7-3.0-1.noarch)
    [02/05/19 18:35:47]     mcp-client-rhel7-3.0-1.noarch removed successfully
    [02/05/19 18:35:47]     Installing new MCP client...
    [02/05/19 18:35:49]     Rebuilding YUM cache...(This will take about 5 minutes)
    [02/05/19 18:38:06]     Done.
    [02/05/19 18:38:07] MCP Client has been successfully updated.
  4. To verify the process succeeded, simply inspect the MCP Client version:

     # rpm -q mcp-client-rhel7mcp-client-rhel7-3.1-1
  5. Notice the MCP client version is now 3.1-1.  This indicates the update/migration was successful.

    Important

    It is extremely rare for the migration process to fail; however, if this version number did not change, this indicates something went wrong. Please contact support and provide the details of the /var/log/rhui-client-install log file.  This file contains information necessary to troubleshoot any issue and provide a solution. 

    After successfully upgrading the MCP client, the server will begin receiving RedHat software package content from the RHUI v3 architecture.


Recently Updated