4.2. Preparing 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)$'

   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)$'

   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

   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

   Use the output of this command to compare after the upgrade is complete.