此内容没有您所选择的语言版本。

4.2. Preparing for an Upgrade


The following instructions describe how to prepare OpenShift Enterprise for an upgrade.

Procedure 4.1. To Prepare OpenShift Enterprise for an Upgrade:

  1. Perform the required backup steps before starting with the upgrade. Only proceed to the next step after the backup is complete, and the relevant personnel are notified of the upcoming outage.
  2. Disable any change management software that is being used to manage your OpenShift Enterprise installation configuration, and update it accordingly after the upgrade.
  3. If a configuration file already exists on disk during an update, the RPM package that provides the file does one of the following, depending on how the package is built:
    • Backs up the existing file with an .rpmsave extension and creates the new file.
    • Leaves the existing file in place and creates the new file with an .rpmnew extension.
    Before updating, find any .rpm* files still on disk from previous updates using the following commands:
    # updatedb
    # locate --regex '\.rpm(save|new)$'
    Copy to Clipboard Toggle word wrap
    Compare these files to the relevant configuration files currently in use and note any differences. Manually merge any desired settings into the current configuration files, then either move the .rpm* files to an archive directory or remove them.
  4. Before attempting to upgrade, ensure the latest errata have been applied for the current minor version of your OpenShift Enterprise installation. Run the yum update command, then check again for any new configuration files that have changed:
    # yum update -y
    # updatedb
    # locate --regex '\.rpm(save|new)$'
    Copy to Clipboard Toggle word wrap
    Resolve any .rpm* files found again as described in the previous step.
    Additional steps may also be required depending on the errata being applied. For more information on errata updates, see the relevant OpenShift Enterprise Release Notes at http://access.redhat.com/site/documentation.
  5. Restart any services that had their configuration files updated.
  6. Run the oo-admin-chk script on a broker host:
    # oo-admin-chk
    Copy to Clipboard Toggle word wrap
    This command checks the integrity of the MongoDB datastore against the actual deployment of application gears on the node hosts. Resolve any issues reported by this script, if possible, prior to performing an upgrade. For more information on using the oo-admin-chk script and fixing gear discrepancies, see the OpenShift Enterprise Troubleshooting Guide at http://access.redhat.com/site/documentation.
  7. Run the oo-diagnostics script on all hosts:
    # oo-diagnostics
    Copy to Clipboard Toggle word wrap
    Use the output of this command to compare after the upgrade is complete.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat