Description

This article describes the steps to configure existing Red Hat Enterprise Linux 5, 6 & 7 servers imported to the Managed Cloud Platform, to use the Red Hat Update Infrastructure hosted on the Managed Cloud Platform.

It is important to note that Red Hat servers that have been configured to use the MCP Update Infrastructure will not work outside of the MCP network. That is, a server exported then imported into another Cloud provider or to an on-premise hypervisor will not be able to access our Update Infrastructure. These servers will need to be relicensed with another provider or directly with Red Hat.

Prerequisites:

From the list below, click the appropriate link to download the RPM package containing the certificate that grants access to the Update Infrastructure. There is a single RPM package for each major release of Red Hat Enterprise Linux, which will work regardless whether it's 32-bit or 64-bit.

Client Config RPMSHA1 Checksum
MCP Client for RHEL5
970f2a273851830eabce4108663e9ed7a9aa4d61
MCP Client for RHEL6
5d058795bac983a118cd1119c79f85ca4c5d0084
MCP Client for RHEL7
5612a5d1037f3ead8af2295f0c15f4b4c638a9ae

Content / Solution:

  1. Transfer the appropriate RPM from the list above to the server to be configured

  2. Rename the current Red Hat Network systemid file:

    # mv /etc/sysconfig/rhn/systemid /etc/sysconfig/rhn/systemid.backup



  3. Install the MCP client configuration package. These are specific to each release of Red Hat so install the version appropriate for your server (the following example uses RHEL 5.):

    # yum localinstall mcp-client-rhel5-3.0-2.noarch.rpm &

    Note: The "&" at the end of the above command will make the process run in the background.  This  allows for monitoring the installation process as outlined below.                                                                                                                                    


  4. This process will take up to 5 minutes to complete, depending on the amount of metadata being cached. All activity is stored in /var/log/install-rhui-client and can be monitored by running the following command:

    # 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-2.noarch)
    [02/05/19 18:35:47] mcp-client-rhel7-3.0-2.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.

    The last four lines in the output show the client being installed, followed by updating the YUM local cache.

Once this process is complete, the server will begin receiving software packages from the MCP RedHat Update Infrastructure