Chapter 4. Asynchronous Errata Updates

Security, bug fix, and enhancement updates for OpenShift Enterprise 2.0 are released as asynchronous errata through the Red Hat Network. All OpenShift Enterprise 2 errata is available on the Red Hat Customer Portal at https://rhn.redhat.com/errata/rhel6-rhose2-errata.html. See https://access.redhat.com/site/support/policy/updates/openshift/ for more information about asynchronous errata.
Red Hat Customer Portal users can enable errata notifications in the account settings for Red Hat Subscription Management (RHSM) or Red Hat Network (RHN) Classic. When errata notifications are enabled, users are notified via email whenever new errata relevant to their registered systems are released.

Note

Red Hat Customer Portal user accounts must have systems registered and consuming OpenShift Enterprise entitlements for OpenShift Enterprise errata notification emails to generate.
Additional Update Instructions per Release

The latest OpenShift Enterprise Deployment Guide provides general instructions on how to apply asynchronous errata updates within a minor release:

https://access.redhat.com/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#Applying_Asynchronous_Errata_Updates
Some errata have additional instructions specific to that release that must be performed to fully apply the update to a host. The general instructions provided in the above OpenShift Enterprise Deployment Guide section reference Table 4.1, “Additional Update Instructions per Release” in this section, which details the releases that require additional steps.
Running the yum update command on a host installs packages for all pending updates at once. If you are applying multiple asynchronous errata updates at once, any additional update instructions for all releases being installed must be performed. However, the steps can be aggregated in this situation when commands would be unnecessarily repeated. When evaluating which additional steps must be performed for multiple pending asynchronous errata updates, consider the following general workflow:
  1. Run the yum update command on each host.
  2. Restart relevant services.
  3. Clear the broker and console cache on the broker host, if relevant.
  4. Run the oo-admin-upgrade command on the broker host to upgrade existing gears, if relevant.
Table 4.1, “Additional Update Instructions per Release” details whether certain parts of the above workflow are relevant to the errata updates you are applying.

Example 4.1. Applying Multiple Asynchronous Errata Updates at Once

For example, if you are updating an OpenShift Enterprise 2.0.2 deployment to release 2.0.7, see Table 4.1, “Additional Update Instructions per Release” and read through any additional instructions for all advisories listed for releases 2.0.3 through 2.0.7. The instructions listed for these releases can be aggregated into the following steps:
  1. After running the yum update command on each host, run the following on each node host: 
    # service ruby193-mcollective restart
  2. Run the following on the broker host: 
    # service openshift-broker restart
# service openshift-console restart
# oo-admin-broker-cache --console
# oo-admin-upgrade archive
# oo-admin-upgrade upgrade-node --version=2.0.7
    Note that the oo-admin-upgrade upgrade-node command is only run once, using the version for the latest release being applied.

Table 4.1. Additional Update Instructions per Release

Release Advisory Additional Instructions
2.0.1 RHBA-2014:0020
After running the yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host: 
# service ruby193-mcollective restart
2.0.2 RHBA-2014:0102
After running the yum update command and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host: 
# service ruby193-mcollective restart
On the broker host, restart the broker service and, if installed, the console service: 
# service openshift-broker restart
# service openshift-console restart
RHBA-2014:0117
After running the yum update command and ensuring all packages have been updated, restart the broker service on the broker host: 
# service openshift-broker restart
2.0.3 RHBA-2014:0209
After running the yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host: 
# service ruby193-mcollective restart
On the broker host, upgrade all nodes using the following commands. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for alternate oo-admin-upgrade command usage and use 2.0.3 as the target --version. 
# rm -rf /tmp/oo-upgrade
# oo-admin-upgrade upgrade-node --version=2.0.3
RHBA-2014:0210
After running the yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host: 
# service ruby193-mcollective restart
On the broker host, upgrade all nodes using the following commands. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for alternate oo-admin-upgrade command usage and use 2.0.3 as the target --version. 
# rm -rf /tmp/oo-upgrade
# oo-admin-upgrade upgrade-node --version=2.0.3
2.0.4 RHBA-2014:0309
After running the yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host: 
# service ruby193-mcollective restart
On the broker host, restart the broker service: 
# service openshift-broker restart
2.0.5 RHBA-2014:0417
After running the yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host: 
# service ruby193-mcollective restart
2.0.6 RHEA-2014:0599
After running the yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host: 
# service ruby193-mcollective restart
On the broker host, restart the broker service and, if installed, the console service: 
# service openshift-broker restart
# service openshift-console restart
Clear the broker cache and, if installed, the console cache: 
# oo-admin-broker-cache --console
On the broker host, archive previous upgrade data and upgrade all nodes using the following commands. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for alternate oo-admin-upgrade command usage and use 2.0.6 as the target --version. 
# oo-admin-upgrade archive
# oo-admin-upgrade upgrade-node --version=2.0.6
2.0.7 RHBA-2014:1097
After running the yum update command on each host and ensuring all packages have been updated, there are no additional update instructions for this release.
2.0.8 RHBA-2015:0053
After running the yum update command on each host and ensuring all packages have been updated, there are no additional update instructions for this release.
2.0.9 RHBA-2015:1588
After running the yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective service on each node host: 
# service ruby193-mcollective restart
Clear the broker cache and, if installed, the console cache: 
# oo-admin-broker-cache --console
2.0.10 RHEA-2015:1587
After running the yum update command on each host and ensuring all packages have been updated, there are no additional update instructions for this release.