Chapter 5. Asynchronous Errata Updates
Security, bug fix, and enhancement updates for OpenShift Enterprise 2.2 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/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. 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 OpenShift Enterprise Deployment Guide reference Table 5.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:
- Run the
yum updatecommand on each host. - Restart relevant services.
- Import, activate, and migrate the latest cartridge manifests on the broker host, if relevant.
- Run the
oo-admin-upgradecommand on the broker host to upgrade existing gears, if relevant.
Table 5.1, “Additional Update Instructions per Release” details whether certain parts of the above workflow are relevant to the errata updates you are applying.
Example 5.1. Applying Multiple Asynchronous Errata Updates at Once
For example, if you are updating an OpenShift Enterprise release 2.2.0 deployment to release 2.2.2, see Table 5.1, “Additional Update Instructions per Release” and read through the additional instructions for releases 2.2.1 and 2.2.2. The instructions listed for these two releases can be aggregated into the following steps:
- After running the
yum updatecommand on each host, run the following on each node host:#
service ruby193-mcollective restart - Restart the routing daemon, if installed:
#
service openshift-routing-daemon restart - Run the following on the broker host:
#
service openshift-broker restart#service openshift-console restart#oo-admin-ctl-cartridge -c import-node --activate --obsolete#oo-admin-ctl-cartridge -c migrate#oo-admin-upgrade archive#oo-admin-upgrade upgrade-node --version=2.2.2Note that theoo-admin-upgrade upgrade-nodecommand is only run once, using the version for the latest release being applied.
| Release | Advisory | Additional Instructions |
|---|---|---|
| 2.2.1 | RHBA-2014:1903 |
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:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.1 as the target --version.
# |
| 2.2.2 | RHBA-2014:1979 |
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:
#
On the broker host, restart the broker service and, if installed, the Management Console service:
#
Restart the routing daemon, if installed:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.2 as the target --version.
# |
| RHBA-2014:1978 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the routing daemon, if installed:
#
| |
| 2.2.3 | RHBA-2015:0019 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective and openshift-watchman services on each node host:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.3 as the target --version.
# |
| 2.2.4 | RHBA-2015:0220 |
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:
#
On the broker host, restart the broker service:
#
Restart the routing daemon, if installed:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.4 as the target --version.
# |
| 2.2.5 | RHBA-2015:0779 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the ruby193-mcollective and openshift-watchman services on each node host:
#
On the broker host, restart the broker service:
#
Restart the routing daemon, if installed:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.5 as the target --version.
# |
| 2.2.6 | RHBA-2015:1463 |
After running the
yum update command on each host and ensuring all packages have been updated, restart the broker service and, if installed, the Management Console service on the broker host:
#
Restart the routing daemon, if installed and integrated with F5 BIG-IP LTM®:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.6 as the target --version.
#
Restart
rsyslog7 on each node host, if installed:
#
|
| 2.2.7 | RHSA-2015:1844 |
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:
#
On the broker host, restart the broker service:
#
Restart the routing daemon, if installed and integrated with F5 BIG-IP LTM®:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.7 as the target --version.
#
Users must restart their gears for the changes in this release to take effect.
|
| 2.2.8 | RHSA-2015:2666 |
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:
#
On the broker host, restart the broker service:
#
Restart the routing daemon, if installed and integrated with F5 BIG-IP LTM®:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.8 as the target --version.
#
Users must restart their gears for the changes in this release to take effect.
|
| 2.2.9 | RHSA-2016:0489 |
After running the
yum update command on each host and ensuring all packages have been updated, restart ActiveMQ on any broker or messaging host running the service:
#
Restart the
ruby193-mcollective service on each node host:
#
On the broker host, restart the broker service and, if installed, the Management Console service:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.9 as the target --version.
#
Users must restart their gears for the changes in this release to take effect.
|
| 2.2.10 | RHSA-2016:1773 |
After running the
yum update command on each host and ensuring all packages have been updated, restart ActiveMQ on any broker or messaging host running the service:
#
Restart the
ruby193-mcollective service on each node host:
#
On the broker host, restart the broker service and, if installed, the Management Console service:
#
Restart the routing daemon, if installed and integrated with F5 BIG-IP LTM®:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.10 as the target --version.
#
Users must restart their gears for the changes in this release to take effect.
|
| 2.2.11 | RHBA-2017:0017 |
After running the
yum update command on each host and ensuring all packages have been updated, restart ActiveMQ on any broker or messaging host running the service:
#
Restart the
ruby193-mcollective service on each node host:
#
On the broker host, restart the broker service and, if installed, the Management Console service:
#
Restart the routing daemon, if installed and integrated with F5 BIG-IP LTM®:
#
On the broker host, import and activate the latest cartridge manifests, then migrate old cartridge versions to the latest active versions. Note that this may also activate cartridges that you have previously deactivated, so you may need to again deactivate any cartridges that you want to remain deactivated.
#
On the broker host, archive previous upgrade data and upgrade all nodes. Alternatively, to only upgrade a single node or gear, see the OpenShift Enterprise Deployment Guide for other
oo-admin-upgrade command usage and use 2.2.11 as the target --version.
#
Users must restart their gears for the changes in this release to take effect.
|
