This topic contains release notes for VMware Tanzu Operations Manager (Ops Manager) v3.0.
You can jump upgrade directly from previous versions of Ops Manager to Ops Manager v3.0. For more information, see Jump Upgrading to Ops Manager v3.0.
For the feature highlights of this release, see New Features in Ops Manager v3.0 below.
Ops Manager is certified by the Cloud Foundry Foundation for 2023.
For more information about the Cloud Foundry Certified Provider Program, see How Do I Become a Certified Provider? on the Cloud Foundry website.
Release Date: March 24, 2023
Caution: This release includes a new version of BOSH DNS. Upgrading to Ops Manager v3.0.6+LTS-T causes all VMs to re-deploy.
[Feature] Logs downloaded from BOSH-deployed VMs through Ops Manager also contain logs from the /var/log directory.
[Known Issue Fix] After you upgrade to Ops Manager v3.0.6+LTS-T, improperly encoded data in the Ops Manager database does not cause re-deployments to fail. For more information about this known issue, see Missing Classes Cause Re-Deployment Failures below.
[Bug Fix] When you retrieve the manifest for a deployed product through the Ops Manager API, the API endpoint no longer returns an invalid manifest.
| Component | Version |
|---|---|
| Tanzu Ops Manager | 3.0.6-build.269* |
| Stemcell (Bosh Director and Ops Manager) | 1.95* |
| BBR SDK | 1.18.62 |
| BOSH Director | 277.3.0 |
| BOSH DNS | 1.36.1* |
| System Metrics | 2.2.7 |
| CredHub | 2.12.23* |
| CredHub Maestro | 9.0.2* |
| Syslog | 12.1.3 |
| Windows Syslog | 1.1.13 |
| UAA | 76.8.0* |
| BPM | 1.1.21 |
| OS Conf | 22.1.2 |
| AWS CPI | 97 |
| Azure CPI | 42.0.0 |
| Google CPI | 46.0.2* |
| OpenStack CPI | 51 |
| vSphere CPI | 90 |
| BOSH CLI | 7.2.0* |
| Credhub CLI | 2.9.13* |
| BBR CLI | 1.9.42* |
| Telemetry | 2.0.5 |
| * Components marked with an asterisk have been updated. | |
Release Date: March 10, 2023
Caution: This release includes a new version of System Metrics. Upgrading to Ops Manager v3.0.5+LTS-T causes all VMs to re-deploy.
[Feature] Ops Manager v3.0 is a long-term support (LTS) version. If you use automation scripts to deploy Ops Manager, you may need to update them in order to install new patch versions. For more information, see Long-Term Support for Ops Manager v3.0 below.
[Feature] You can rotate non-configurable leaf certificates through the Review Pending Changes page in the Ops Manager Installation Dashboard. For more information, see Rotate Non-Configurable Leaf Certificates During Re-Deployment below.
[Feature] You can configure your VMs to use short-lived NATS credentials during the bootstrap process. For more information, see Short-Lived NATS Bootstrap Credentials below.
[Feature Improvement] Ops Manager v3.0 uses Rails 7.0.
[Feature Improvement] Ops Manager v3.0 uses Node 18.
[Feature Improvement] In the Ops Manager Installation Dashboard, load times and caching for the Stemcell Library page are improved.
[Known Issue Fix] Upgrading from previous versions of Ops Manager does not corrupt the PostgreSQL database indexes in the BOSH Director. For more information about this known issue, see Upgrading Ops Manager Corrupts BOSH Director PostgreSQL Database Indexes below.
[Known Issue] After you upgrade to Ops Manager v3.0.5+LTS-T, improperly encoded data in the Ops Manager database can cause re-deployments to fail. For more information, see Missing Classes Cause Re-Deployment Failures below.
[Bug Fix] Temporary verifier failures are properly exposed and do not cause a 500 error.
[Bug Fix] In the Ops Manager Installation Dashboard, the Review Pending Changes page does not show a Stemcell Out of Date status when you are using the most recent stemcell versions.
| Component | Version |
|---|---|
| Tanzu Ops Manager | 3.0.5-build.251* |
| Stemcell (BOSH Director and Ops Manager) | 1.93* |
| BBR SDK | 1.18.62* |
| BOSH Director | 277.3.0* |
| BOSH DNS | 1.36.0 |
| System Metrics | 2.2.7* |
| CredHub | 2.12.21* |
| CredHub Maestro | 9.0.1* |
| Syslog | 12.1.3* |
| Windows Syslog | 1.1.13* |
| UAA | 76.7.0* |
| BPM | 1.1.21 |
| OS Conf | 22.1.2 |
| AWS CPI | 97* |
| Azure CPI | 42.0.0* |
| Google CPI | 46.0.1 |
| OpenStack CPI | 51 |
| vSphere CPI | 90* |
| BOSH CLI | 7.1.3* |
| Credhub CLI | 2.9.12* |
| BBR CLI | 1.9.41* |
| Telemetry | 2.0.5 |
| * Components marked with an asterisk have been updated. | |
Release Date: February 09, 2023
Caution: This release includes new versions of BOSH DNS and System Metrics. Upgrading to Ops Manager v3.0.4 causes all VMs to re-deploy.
[Feature] The Ops Manager Installation Dashboard uses more inclusive text.
[Bug Fix] When you click See Changes, secrets are correctly redacted from Ops Manager production logs.
| Component | Version |
|---|---|
| Tanzu Ops Manager | 3.0.4-build.227* |
| Stemcell (BOSH Director and Ops Manager) | 1.83* |
| BBR SDK | 1.18.61* |
| BOSH Director | 276.1.1 |
| BOSH DNS | 1.36.0* |
| System Metrics | 2.2.5* |
| CredHub | 2.12.19* |
| CredHub Maestro | 8.0.9* |
| Syslog | 12.1.1 |
| Windows Syslog | 1.1.11 |
| UAA | 74.5.63* |
| BPM | 1.1.21 |
| OS Conf | 22.1.2 |
| AWS CPI | 96 |
| Azure CPI | 41.0.0 |
| Google CPI | 46.0.1* |
| OpenStack CPI | 51 |
| vSphere CPI | 89* |
| BOSH CLI | 7.1.2* |
| Credhub CLI | 2.9.10* |
| BBR CLI | 1.9.39* |
| Telemetry | 2.0.5* |
| * Components marked with an asterisk have been updated. | |
Release Date: January 06, 2023
[Feature] The ephemeral disk size of e2-highmem-4 and e2-highmem-8 VM types is increased.
[Feature] You can download logs directly from the Status page in the Ops Manager Installation Dashboard.
[Feature] Ops Manager creates additional logs to track when tile migrations are applied. This allows VMware to better use logs to debug issues with tile upgrade failures.
| Component | Version |
|---|---|
| Tanzu Ops Manager | 3.0.3-build.203* |
| Stemcell (BOSH Director and Ops Manager) | 1.75* |
| BBR SDK | 1.18.60* |
| BOSH Director | 276.1.1 |
| BOSH DNS | 1.34.0 |
| System Metrics | 2.2.4 |
| CredHub | 2.12.18 |
| CredHub Maestro | 8.0.8 |
| Syslog | 12.1.1 |
| Windows Syslog | 1.1.11 |
| UAA | 74.5.61 |
| BPM | 1.1.21 |
| OS Conf | 22.1.2 |
| AWS CPI | 96 |
| Azure CPI | 41.0.0 |
| Google CPI | 46.0.0* |
| OpenStack CPI | 51 |
| vSphere CPI | 88* |
| BOSH CLI | 7.1.0 |
| Credhub CLI | 2.9.9 |
| BBR CLI | 1.9.38 |
| Telemetry | 2.0.2 |
| * Components marked with an asterisk have been updated. | |
Release Date: December 16, 2022
Caution: This release includes a new version of System Metrics. Upgrading to Ops Manager v3.0.2 causes all VMs to re-deploy.
| Component | Version |
|---|---|
| Tanzu Ops Manager | 3.0.2-build.192* |
| Stemcell (BOSH Director and Ops Manager) | 1.71* |
| BBR SDK | 1.18.59 |
| BOSH Director | 276.1.1 |
| BOSH DNS | 1.34.0 |
| System Metrics | 2.2.4* |
| CredHub | 2.12.18* |
| CredHub Maestro | 8.0.8 |
| Syslog | 12.1.1 |
| Windows Syslog | 1.1.11 |
| UAA | 74.5.61* |
| BPM | 1.1.21 |
| OS Conf | 22.1.2 |
| AWS CPI | 96 |
| Azure CPI | 41.0.0 |
| Google CPI | 45.0.0 |
| OpenStack CPI | 51 |
| vSphere CPI | 87 |
| BOSH CLI | 7.1.0 |
| Credhub CLI | 2.9.9* |
| BBR CLI | 1.9.38 |
| Telemetry | 2.0.2 |
| * Components marked with an asterisk have been updated. | |
Release Date: December 09, 2022
Caution: This release includes a new version of System Metrics. Upgrading to Ops Manager v3.0.1 causes all VMs to re-deploy.
[Feature] BOSH Director is deployed with PostgreSQL 13.
[Feature] Keyboard accessibility for navigating the Ops Manager Installation Dashboard is improved.
[Bug Fix] When you export your installation settings, files on disk are properly cleaned up.
[Bug Fix] Deploying the BOSH Director in an air-gapped environment no longer causes an error.
| Component | Version |
|---|---|
| Tanzu Ops Manager | 3.0.1-build.184* |
| Stemcell (BOSH Director and Ops Manager) | 1.64* |
| BBR SDK | 1.18.59* |
| BOSH Director | 276.1.1* |
| BOSH DNS | 1.34.0 |
| System Metrics | 2.2.3* |
| CredHub | 2.12.16* |
| CredHub Maestro | 8.0.8* |
| Syslog | 12.1.1* |
| Windows Syslog | 1.1.11 |
| UAA | 74.5.60* |
| BPM | 1.1.21* |
| OS Conf | 22.1.2 |
| AWS CPI | 96* |
| Azure CPI | 41.0.0 |
| Google CPI | 45.0.0 |
| OpenStack CPI | 51 |
| vSphere CPI | 87 |
| BOSH CLI | 7.1.0* |
| Credhub CLI | 2.9.8 |
| BBR CLI | 1.9.38 |
| Telemetry | 2.0.2* |
| * Components marked with an asterisk have been updated. | |
Release Date: November 15, 2022
Ops Manager v3.0.0 uses the following component versions:
| Component | Version |
|---|---|
| Tanzu Ops Manager | 3.0.0-build.158 |
| Stemcell (BOSH Director and Ops Manager) | 1.44 |
| BBR SDK | 1.18.57 |
| BOSH Director | 276.1.0 |
| BOSH DNS | 1.34.0 |
| System Metrics | 2.2.2 |
| CredHub | 2.12.13 |
| CredHub Maestro | 8.0.7 |
| Syslog | 12.0.6 |
| Windows Syslog | 1.1.11 |
| UAA | 74.5.58 |
| BPM | 1.1.19 |
| OS Conf | 22.1.2 |
| AWS CPI | 95 |
| Azure CPI | 41.0.0 |
| Google CPI | 45.0.0 |
| OpenStack CPI | 51 |
| vSphere CPI | 87 |
| BOSH CLI | 7.0.1 |
| Credhub CLI | 2.9.8 |
| BBR CLI | 1.9.38 |
| Telemetry | 2.0.1 |
To upgrade to Ops Manager v3.0, see Upgrading Ops Manager.
Ops Manager v3.0 includes the following major features:
Ops Manager v3.0 is a long-term support (LTS) version of Ops Manager. Ops Manager v3.0 is to be supported through March 2025.
Over the lifecycle of Ops Manager v3.0, VMware will release security patches that occasionally include feature improvements and maintenance updates.
Versions and filenames for Ops Manager v3.0 releases on VMware Tanzu Network include a +LTS-T suffix to indicate its LTS status. If you use automation scripts to deploy Ops Manager, you may need to update them to include this suffix in your version and filename patterns. For example, the filename for the Azure version of Ops Manager v3.0.4 is ops-manager-azure-3.0.4-build.227.yml, while the filename for the Azure version of Ops Manager v3.0.5+LTS-T is ops-manager-azure-3.0.5+LTS-T.yml.
You can jump upgrade directly from previous versions of Ops Manager to Ops Manager v3.0. For more information, see Jump Upgrading to Ops Manager v3.0.
Ops Manager v3.0 uses Jammy Jellyfish, a Jammy stemcell based on Ubuntu 22.04.
The previously-supported Xenial Xerus stemcells were based on Ubuntu 16.04. These stemcells are due to reach end of general support (EOGS) and stop receiving security updates in April 2024. You can still use Xenial stemcells with tiles installed on Ops Manager v3.0 until they reach EOGS.
Ops Manager v3.0 allows tile authors to upgrade from Xenial stemcells to Jammy Jellyfish stemcells. This ensures that Ops Manager v3.0 users can maintain access to secure stemcells.
In the Ops Manager Installation Dashboard, the Review Pending Changes page for a tile includes a list of runtime configurations to be applied to that tile.
Tiles can use runtime configurations to influence the behavior of VMs that other tiles deploy. For example, when you activate the Enable additional System Metrics checkbox in the Director Config pane of the BOSH Director tile, the BOSH Director applies a runtime configuration to the VMs that VMware Tanzu Application Service for VMs (TAS for VMs) deploys. This configuration allows the BOSH Director to collect detailed metrics from VMs managed by TAS for VMs.
Changes to a runtime configuration can cause longer deployment times when you re-deploy a tile. By reviewing the runtime configurations that are to be applied to tiles during re-deployment, you can determine in advance which tiles may take a longer time to re-deploy.
Ops Manager v3.0 uses 5th-generation AMD instances for AWS deployments. 5th-generation AMD instances have better performance characteristics and are more cost-effective than previous instance types. Both Jammy Jellyfish stemcells and Xenial stemcells support 5th-generation AMD instances.
New installations of Ops Manager v3.0 use 5th-generation AMD instances by default. If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, you can either keep your current VM types or convert your VMs to 5th-generation AMD instances in the AWS Config pane of the BOSH Director tile. For more information, see Step 2: AWS Config Page in Configuring BOSH Director on AWS.
If you are using a custom instance type catalog, the VM types that you can use do not change.
The 5th-generation AMD instances are closer to the recommended default size for tiles. Because of this, product tiles in Ops Manager select VM types that are smaller than the previous sizes for their jobs. For example, Diego Cells select an instance type with 2 CPUs and 16 GB of RAM. When you convert your VMs to 5th-generation AMD instances, you may need to either scale up the number of Diego Cell instances or change the selected VM type of certain jobs to a larger VM type. You can configure both the number of instances and VM type of each job in the Resource Config pane of a product tile.
For more information about AWS Linux instance types, see the AWS documentation. For more information about AWS Windows instance types, see the AWS documentation.
Ops Manager v3.0 uses gp3 disks for AWS deployments. The gp3 disks have better performance characteristics and are more cost-effective than gp2 disks.
New installations of Ops Manager v3.0 use gp3 disks by default. If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, you can either keep your current disk types or convert your disks to gp3 in the AWS Config pane of the BOSH Director tile. For more information, see Step 2: AWS Config Page in Configuring BOSH Director on AWS.
Ops Manager v3.0 uses E2 Series instances for GCP deployments. E2 Series instances have better performance characteristics and are more cost-effective than previous instance types. Both Jammy Jellyfish stemcells and Xenial stemcells support E2 Series instances.
New installations of Ops Manager v3.0 use E2 Series instances by default. If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, you can either keep your current VM types or convert your VMs to E2 Series instances in the Google Config pane of the BOSH Director tile. For more information, see Step 2: Configure GCP Tile in Configuring BOSH Director on GCP.
If you are using a custom instance type catalog, the VM types you can use do not change.
The E2 Series instances are closer to the recommended default size for tiles. Because of this, product tiles in Ops Manager select VM types that are smaller than the previous sizes for their jobs. For example, Diego Cells select an instance type with 2 CPUs and 16 GB of RAM. When you convert your VMs to E2 Series instances, you may need to either scale up the number of Diego Cell instances or change the selected VM type of certain jobs to a larger VM type. You can configure both the number of instances and VM type of each job in the Resource Config pane of a product tile.
For more information about GCP instance types, see the GCP documentation.
Ops Manager v3.0 allows you to include machine types in your custom VM type catalogs for GCP deployments. When you configure VMs to use a specific machine type, the BOSH Director creates VMs using that machine type, rather than creating a custom VM that matches the CPU and RAM specifications. This allows you to use specialized VM types that are not in the default Ops Manager VM type catalog.
If you do not specify a machine type as a custom VM type, the BOSH Director continues to create VMs that match the CPU and RAM specifications.
For more information about custom VM type catalogs for GCP deployments, see the Ops Manager API documentation.
In Ops Manager v3.0, the Director Config pane includes the Enable Short Lived NATS Bootstrap Credentials checkbox. Activating this checkbox configures your VMs to use short-lived NATS credentials during the bootstrap process. This increases the security of your Ops Manager deployment by rotating the TLS certificate that the BOSH Agents in your VMs use to communicate with the BOSH Director through BOSH NATS.
For more information about short-lived NATS bootstrap credentials, see Using Short-Lived NATS Bootstrap Credentials.
In Ops Manager v3.0, the Review Pending Changes page in the Ops Manager Installation Dashboard includes the Rotate All Non-Configurable Leaf Certificates checkbox. Activating this checkbox allows you to rotate non-configurable leaf certificates when you re-deploy your tiles through the Ops Manager Installation Dashboard, instead of having to rotate them through the Ops Manager API.
For more information about rotating non-configurable leaf certificates through the Ops Manager Installation Dashboard, see Review Pending Changes Page in Reviewing Pending Product Changes.
Ops Manager v3.0 includes the following breaking changes:
The BOSH System Metrics Server is removed from Ops Manager v3.0.
If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, and you previously configured the BOSH Director to deploy the BOSH System Metrics Server, you must deactivate the Enable deprecated BOSH System Metrics Server checkbox and activate the Enable additional System Metrics checkbox in the Director Config pane of the BOSH Director tile before you begin upgrading. In Ops Manager v3.0, the Enable BOSH System Metrics Server checkbox is removed from the BOSH Director tile.
NSX-V networking reached EOGS in January 2022. Because of this, you cannot configure NSX-V networking in Ops Manager v3.0.
You can still configure NSX-T networking for compatible vSphere deployments. For more information, see Resource Requirements in Installing Ops Manager on vSphere.
In Ops Manager v3.0, Keystone v2 is removed and replaced by Keystone v3 for user authentication in OpenStack deployments.
If you upgrade to Ops Manager v3.0 from Ops Manager v2.10 or earlier, and you previously used Keystone v2 to authenticate users, you must re-configure your deployment to use Keystone v3 authentication before you begin upgrading.
Ops Manager v2.10 and earlier include an undocumented API endpoint that allows you to configure a second network on the BOSH Director VM. In Ops Manager v3.0, this API endpoint is removed, and you can no longer configure a second network on the BOSH Director VM.
As of 2021, Microsoft has discontinued the Azure Germany cloud platform. Because of this, you cannot configure an Azure Germany environment in Ops Manager v3.0. However, you can still use Germany-based regions in the global Azure Commercial Cloud environment.
You also cannot configure an Azure Stack environment in Ops Manager v3.0.
In Ops Manager v3.0, invalid custom syslog rules cause Ops Manager deployments to fail with a relevant error message. In Ops Manager v2.10 and earlier, invalid custom syslog rules only cause Ops Manager to log errors and discard the invalid rules.
To avoid deployment failure, validate your custom syslog configuration in one of the following ways:
As your syslog server is pre-starting, look for a Custom rule configuration invalid error message. This error message indicates that one or more of your custom syslog rules are invalid. You can then edit these custom rules accordingly in the Custom rsyslog Configuration field in the Syslog pane of the BOSH Director tile.
In a terminal window, run the following command in a local environment:
rsyslogd -N1
In Ops Manager v3.0 includes the following known issues:
In Ops Manager v3.0, the BOSH Director is deployed using a Jammy stemcell. In Ops Manager v2.10 and earlier, the BOSH Director is deployed using a Xenial stemcell, which uses a different version of glibc. When you upgrade to Ops Manager v3.0 from an earlier version, the difference in the string collation for glibc can cause the indexes of the PostgreSQL database in the BOSH Director to become corrupt. As a result, upgrading to Ops Manager v3.0 can cause the BOSH Director to fail.
This issue is resolved in Ops Manager v3.0.5+LTS-T. If you previously upgraded to Ops Manager v3.0 from an earlier version and have already encountered this issue, upgrading to Ops Manager v3.0.5+LTS-T may cause your Ops Manager deployment to fail. If this happens, contact Support for assistance.
After you upgrade to Ops Manager v3.0.5+LTS-T, improperly encoded data in the Ops Manager database can cause errors similar to the following example when you re-deploy Ops Manager:
Error in step runner run method (will show -1 as exit code): Tried to load unspecified class: ActiveSupport::HashWithIndifferentAccess
As a result, Ops Manager fails to re-deploy.
To see whether improperly encoded data exists in your Ops Manager database:
In a browser window, navigate to https://OPS-MANAGER-FQDN/debug/files, where OPS-MANAGER-FQDN is the fully-qualified domain name (FQDN) for your Ops Manager deployment.
After you have reached the page described in the previous step, search the page for HashWithIndifferentAccess. If the HashWithIndifferentAccess string appears on the page, the database for your Ops Manager deployment contains the improperly encoded data that causes Ops Manager re-deployments to fail.
This issue is resolved in Ops Manager v3.0.6+LTS-T.
