1.2. Upgrading OpenShift Enterprise

OpenShift Enterprise relies on a complex set of dependencies; to avoid problems, caution is required when applying software upgrades to broker and node hosts.

For bug fixes and other targeted changes, updated RPMs are released in existing channels. Read errata advisories carefully for instructions on how to safely apply upgrades and details of required service restarts and configuration changes. For example, when upgrading rubygem packages required by the broker application, it is necessary to restart the openshift-broker service. This step regenerates the bundler utility's Gemfile.lock file and allows the broker application and related administrative commands to use the updated gems. See the latest OpenShift Enterprise Deployment Guide at https://access.redhat.com/site/documentation for instructions on how to apply asynchronous errata updates.

For systemic upgrades from previous versions of OpenShift Enterprise requiring formal migration scripts and lockstep package updates, see the latest OpenShift Enterprise Deployment Guide at https://access.redhat.com/site/documentation for instructions on how to use the ose-upgrade tool.