7.2. Configuring Yum on Broker Hosts

The packages required for running OpenShift Enterprise are all available from Red Hat Network (RHN). Third-party RPM repositories and even other products provided by Red Hat can create conflicts with OpenShift Enterprise during initial deployment and later when applying updates. To avoid these issues, it is best to use a combination of the yum-plugin-priorities package and exclude directives in the yum configuration files.
The yum-plugin-priorities package helps prevent other repositories from interfering with Red Hat Network content for OpenShift Enterprise. The exclude directives work around the cases that priorities will not solve. The oo-admin-yum-validator tool consolidates this yum configuration process for specified component types called roles.
Using the oo-admin-yum-validator Tool

After configuring the selected subscription method as described in Section 7.1, “Configuring Broker Host Entitlements”, use the oo-admin-yum-validator tool to configure yum and prepare your host to install the broker components. This tool reports a set of problems, provides recommendations, and halts by default so that you can review each set of proposed changes. You then have the option to apply the changes manually, or let the tool attempt to fix the issues that have been found. This process may require you to run the tool several times. You also have the option of having the tool both report all found issues, and attempt to fix all issues.

Procedure 7.3. To Configure Yum on Broker Hosts:

  1. Install the latest openshift-enterprise-release package: 
    # yum install openshift-enterprise-release
  2. Run the oo-admin-yum-validator command with the -o option for version 2.2 and the -r option for the broker role. This reports the first detected set of problems, provides a set of proposed changes, and halts.

    Example 7.3. Detecting Problems

    # oo-admin-yum-validator -o 2.2 -r broker
				
Please note: --role=broker implicitly enables --role=client to ensure /usr/bin/rhc is available for testing and troubleshooting.
Detected OpenShift Enterprise repository subscription managed by Red Hat Subscription Manager.

The required OpenShift Enterprise repositories are disabled:
    rhel-server-rhscl-6-rpms
    rhel-6-server-ose-2.2-rhc-rpms
    rhel-6-server-rpms
Enable these repositories by running these commands:
# subscription-manager repos --enable=rhel-server-rhscl-6-rpms
# subscription-manager repos --enable=rhel-6-server-ose-2.2-rhc-rpms
# subscription-manager repos --enable=rhel-6-server-rpms
Please re-run this tool after making any recommended repairs to this system
    Alternatively, use the --report-all option to report all detected problems. 
    # oo-admin-yum-validator -o 2.2 -r broker --report-all
  3. After reviewing the reported problems and their proposed changes, either fix them manually or let the tool attempt to fix the first set of problems using the same command with the --fix option. This may require several repeats of steps 2 and 3.

    Example 7.4. Fixing Problems

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

Please note: --role=broker implicitly enables --role=client to ensure /usr/bin/rhc is available for testing and troubleshooting.
Detected OpenShift Enterprise repository subscription managed by Red Hat Subscription Manager.

Enabled repository rhel-server-rhscl-6-rpms
Enabled repository rhel-6-server-ose-2.2-rhc-rpms
Enabled repository rhel-6-server-rpms
    Alternatively, use the --fix-all option to allow the tool to attempt to fix all of the problems that are found. 
    # oo-admin-yum-validator -o 2.2 -r broker --fix-all

    Note

    If the host is using Red Hat Network (RHN) Classic, the --fix and --fix-all options do not automatically enable any missing OpenShift Enterprise channels as they do when the host is using Red Hat Subscription Management. Enable the recommended channels with the rhn-channel command. Replace repo-id in the following command with the repository ID reported in the oo-admin-yum-validator command output. 
    # rhn-channel -a -c repo-id

    Important

    For either subscription method, the --fix and --fix-all options do not automatically install any packages. The tool reports if any manual steps are required.
  4. Repeat steps 2 and 3 until the oo-admin-yum-validator command displays the following message. 
    No problems could be detected!