Ops Manager and Runtime Breaking Changes
This topic describes the breaking changes you need to be aware of when upgrading to v2.9. For more information about important preparation steps you must follow before beginning an upgrade, see Upgrading Ops Manager.
In addition, this topic lists of components that are either at their end-of-life (EOL) or nearing EOL. Components that are EOL may impact certain apps or deployments that depend on them.
For more information, see End-of-Life Components.
See the following Ops Manager v2.9 breaking changes:
Before performing certificate rotation with Ops Manager v2.9, you must first upgrade both Ops Manager and VMware Tanzu Application Service for VMs (TAS for VMs) to v2.9.
If you rotate certificates with Ops Manager v2.9 and Pivotal Application Service (PAS) v2.8, you can orphan VMs.
Not all Ops Manager service tiles are compatible with CredHub Maestro. If you use CredHub Maestro to rotate the services TLS certificate authority (CA) and you have incompatible tiles in your deployment, then you may experience services downtime or data loss.
Before rotating the services TLS CA with CredHub Maestro, you must check that the tiles in your deployment are compatible. For compatibility information, see CredHub Maestro Tile Compatibility.
To rotate the services TLS CA, see Advanced Certificate Rotation with CredHub Maestro.
The BOSH vSphere CPI included with Ops Manager v2.9 does not support NSX-T v2.2 or earlier.
If you are running NSX-T v2.2 or earlier, you must upgrade NSX-T before deploying Ops Manager v2.9.
See the following TAS for VMs v2.9 breaking changes:
This breaking change applies only to deployments where the following conditions are met:
In the Databases pane, PAS v2.8 is configured to use an external GCP or Azure database.
In TAS for VMs v2.9, you want to use the same external GCP or Azure database configured in the Databases pane.
You enabled TLS communication for the GCP or Azure external database by adding a certificate authority (CA) certificate to the Database CA certificate field in the Databases pane.
If your deployment meets these conditions, you must disable hostname validation before you upgrade to v2.9. Failure to disable hostname validation can cause the upgrade to fail for deployments that use external databases on GCP or Azure.
For more information about disabling hostname validation, see Disable Hostname Validation for External Databases on GCP and Azure in Upgrade Preparation Checklist.
There are no breaking changes in this release of TAS for VMs [Windows].
There are no breaking changes in this release of Isolation Segment.
This section lists of components that are either at their end-of-life (EOL) or nearing EOL.
This section lists support changes to buildpacks associated with this release:
.NET Core Buildpack: Support for dotnet-runtime versions 3.0.x will be removed in the first release of the .NET Core buildpack after March 3, 2020.
Node.js Buildpack: Node.js v8.x is removed from the Node.js buildpack v1.7.9 and later because Node.js v8.x is out of support. This removal is known to break App Metrics v1.6.0 to v1.6.2 since those versions of App Metrics rely on Node.js v8.0.
Python: Python v2.7 is removed from the buildpack that ships with TAS for VMs v2.9.0.
If your app depends on any of these language distributions and use the buildpacks packaged for TAS for VMs, you should consider updating the apps and their dependencies prior to upgrading to TAS for VMs v2.9.0.
Shortly after Ops Manager and TAS for VMs v2.9 are released, Ops Manager v2.6 and PAS v2.6 reach their end of general support.