Red Hat SummitDieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
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:
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:
- Run the
yum updatecommand on each host. - Restart relevant services.
- Clear the broker and console cache on the broker host, if relevant.
- Run the
oo-admin-upgradecommand 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:
- After running the
yum updatecommand on each host, run the following on each node host:# service ruby193-mcollective restart - 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.7Note that theoo-admin-upgrade upgrade-nodecommand is only run once, using the version for the latest release being applied.
| 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:
|
| 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:
On the broker host, restart the broker service and, if installed, the console service:
|
| RHBA-2014:0117 |
After running the
yum update command and ensuring all packages have been updated, restart the broker service on the broker host:
| |
| 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:
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.
|
| 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:
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.
| |
| 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:
On the broker host, restart the broker service:
|
| 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:
|
| 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:
On the broker host, restart the broker service and, if installed, the console service:
Clear the broker cache and, if installed, the console cache:
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.
|
| 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:
Clear the broker cache and, if installed, the console cache:
|
| 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.
|
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}