Jump Upgrading to Ops Manager v2.10

Page last updated:

This topic describes upgrading to Ops Manager v2.10.2 directly from Ops Manager v2.4 and later.

Overview

Jump upgrading describes the process of skipping minor versions when upgrading Ops Manager. Jump upgrading enables you to upgrade directly to the long-term support (LTS) version of Ops Manager, which is v2.10. Ops Manager v2.10 is supported through April 2024. For more information, see Long-Term Support for Ops Manager v2.10 in Ops Manager v2.10 Release Notes.

Prerequisites

Before you jump upgrade to Ops Manager v2.10.2:

  • If you are on Ops Manager v2.3 or earlier, you must upgrade to v2.4 before you can jump upgrade to v2.10.2.

  • You must upgrade to Ops Manager v2.10.2 or later.

  • To upgrade to Ops Manager v2.10, you must ensure that the products you have installed are compatible with Ops Manager v2.10.2. To create an upgrade path for your product tiles, see the Upgrade Planner.

  • You must have no changes to any product tile or service instance currently staged.

  • If you are using vSphere with NSX-T, you must have NSX-T v2.3 or later installed.

  • You have installed Trusty stemcell 3541 or later.

Jump Upgrade

After you ensure your deployment meets the requirements described in Prerequisites above, you can upgrade to Ops Manager to v2.10.2 or later.

To jump upgrade to Ops Manager to v2.10.2 or later:

  1. Review the table in Breaking Changes below and address any breaking changes that apply to your current Ops Manager version.

  2. Follow the procedure in Upgrading Ops Manager.

Breaking Changes

The table below describes the breaking changes that affect Ops Manager v2.4 through v2.8 and how to address them before upgrading:

Upgrading From Breaking Change Action Before Upgrading
v2.4 Ops Manager release artifacts are renamed for smoother automation. This could cause your pipeline jobs break due to outdated product filenames. If you use automation scripts or other tools to access release artifacts, update them to match the new filename scheme. For more information, see Ops Manager 2.5 changing the file naming scheme might break the pipeline jobs in the Knowledge Base.
v2.5 You can only SSH onto the Ops Manager VM in a vSphere deployment with a private SSH key, not a password. You could get an error when authenticating that causes Ops Manager to shut down and enter a reboot loop. Add a public key to the OVF template for the Ops Manager VM. Then, use the private key to SSH onto the Ops Manager VM. For more information, see Deploy Ops Manager in Deploying Ops Manager on vSphere.
v2.4 and v2.5 The stemcell property for the Ops Manager API /api/v0/diagnostic_report endpoint is removed. This could cause an error when retrieving Ops Manager diagnostic reports. Update any automation scripts that use the stemcell property. For more information, see Stemcell Property for Diagnostic Report API Endpoint is Removed in Ops Manager v2.6 Release Notes.
v2.4 and v2.5 The stemcell version key for pending changes is moved and renamed. This could cause an error when retrieving Ops Manager API pending changes. Update your automation scripts that use the stemcell information in the /api/v0/pending_changes endpoint. For more information, see View a list of pending changes in the Ops Manager API documentation.
v2.4 and v2.5 Trusty stemcells 3541 and earlier are no longer supported. If your deployment is on AWS and using outdated stemcells, Ops Manager fails to boot. Install Xenial stemcells or Trusty stemcell 3586 or later. For more information, see AWS Deployments Use 5th Generation Instances in Ops Manager v2.6 Release Notes.
v2.4, v2.5, and v2.6 The /api/v0/stemcells_assignments endpoint in the Ops Manager API is removed. This could cause an error when retrieving Ops Manager API stemcell assignments. Update your automation scripts to use the /api/v0/stemcell_associations endpoint instead. For more information, see Stemcell Associations for Products in the Ops Manager API documentation.
v2.4, v2.5, and v2.6 Ops Manager v2.10 installs a later version of the BOSH CLI. This could cause your BOSH CLI automation scripts to stop working. Update your automation scripts to use BOSH CLI v2. For more information, see Installing the CLI and Commands in the BOSH documentation.
v2.4, v2.5, and v2.6 Certain properties within a collection or selector are no longer configurable in the Ops Manager UI and API. Update your automation scripts to remove these properties. For more information about the tile properties you can configure in Ops Manager v2.10.2, see the release notes for that tile.
v2.4, v2.5, and v2.6 The nsx_security_groups property is renamed security_groups for NSX-V deployments and ns_groups for NSX-T deployments. Additionally, the Ops Manager API does not recognize NSX-related properties that are not nested under an nsx or nsxt key. If your deployment is on vSphere, Ops Manager API does not update parameters for NSX-V or NSX-T. Update your automation scripts to use the appropriate properties for your deployment. For more information, see Configuring resources for a job in the Ops Manager API documentation.
v2.4, v2.5, v2.6, v2.7, and v2.8 Ops Manager v2.9 is incompatible with vSphere Data Center NSX-T v2.2 and earlier. Upgrade to NSX-T v2.3 or later. For more information, see Ops Manager v2.9 Incompatible with vSphere Data Center NSX-T v2.2 and Earlier in Ops Manager v2.9 Release Notes.