Release Notes

Note: Pivotal Platform is now part of VMware Tanzu. In v2.8 and later, MySQL for Pivotal Platform is named MySQL for VMware Tanzu.

Page last updated:

VMware recommends that you upgrade to the latest version of your current minor line, then upgrade to the latest available version of the new minor line. For example, if you use an older v2.7.x version, upgrade to the latest v2.7.x version before upgrading to the latest v2.8.x version.

For product versions and upgrade paths, see Upgrade Planner.

v2.8.4

Release Date: November 6, 2020

Features

New features and changes in this release:

• Multi-Site Replication GA: The Multi-Site Replication feature is officially generally available in this release. There have been no changes to the feature since v2.8.3.
• Removed global service instance quota limit: Previously, operators could not set the maximum service instances quota higher than 500 service instances. This upper limit has been removed.
• Percona Server: Upgraded to v5.7.31-34
• Percona XtraDB Cluster: Upgraded to v5.7.31-34
  • This Percona XtraDB Cluster version contains a patch for a remote code execution vulnerability, CVE-2020-15180. For more information, see Percona’s blog post.

Known Issues

This release has the following issues:

• Multi-Site Replication is unsupported for TAS for VMs v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in TAS for VMs v2.6.

• For Ops Manager v2.6 and earlier, automated backups using SCP silently fail: For workaround instructions, see MySQL SCP backups are failing when prompting for the SSH key passphrase in PCF in the VMware Tanzu Network knowledge base.

• MySQL Connector/J 8.0.13 and later does not verify TLS connections: If you use MySQL Connector/J 8.0.13 or later with MySQL for VMware Tanzu, you must modify the JDBC URL in VCAP_SERVICES to include sslMode=VERIFY_IDENTITY and verifyServerCertificate=true.
  
  For more information about JDBC URL syntax, see the MySQL documentation. For more information about VCAP_SERVICES, see MySQL Environment Variables.

• Plan 1 must be active: If you set Plan 1 to Inactive in the MySQL for VMware Tanzu tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.

Compatibility

The following components are compatible with this release:

* Components marked with an asterisk have been updated

v2.8.3

Release Date: October 1, 2020

Resolved Issues

This release has the following fixes:

• Uppercase letters in the Service Network no longer prevents configuration of Multi-Site Replication: Previously, if you had configured the Services Network name with upper case letters in your environment, multi-site replication could not be configured successfully.

Known Issues

This release has the following issues:

• Multi-Site Replication is unsupported for TAS for VMs v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in TAS for VMs v2.6.

• For Ops Manager v2.6 and earlier, automated backups using SCP silently fail: For workaround instructions, see MySQL SCP backups are failing when prompting for the SSH key passphrase in PCF in the VMware Tanzu Network knowledge base.

• MySQL Connector/J 8.0.13 and later does not verify TLS connections: If you use MySQL Connector/J 8.0.13 or later with MySQL for VMware Tanzu, you must modify the JDBC URL in VCAP_SERVICES to include sslMode=VERIFY_IDENTITY and verifyServerCertificate=true.
  
  For more information about JDBC URL syntax, see the MySQL documentation. For more information about VCAP_SERVICES, see MySQL Environment Variables.

• Plan 1 must be active: If you set Plan 1 to Inactive in the MySQL for VMware Tanzu tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.

Compatibility

The following components are compatible with this release:

* Components marked with an asterisk have been updated

v2.8.2

Release Date: September 14, 2020

Features

New features and changes in this release:

• Percona Server: Upgraded to v5.7.30-33
• Percona XtraDB Cluster: Upgraded to v5.7.30-31.43

Known Issues

This release has the following issues:

• Uppercase letters in the service network name blocks Multi-Site Replication setup: BOSH DNS can only resolve lowercase letters. Because the service network name is only used to reference the network configuration in BOSH, change the network name to lowercase letters.

• Multi-Site Replication is unsupported for TAS for VMs v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in TAS for VMs v2.6.

• For Ops Manager v2.6 and earlier, automated backups using SCP silently fail: For workaround instructions, see MySQL SCP backups are failing when prompting for the SSH key passphrase in PCF in the VMware Tanzu Network knowledge base.

• MySQL Connector/J 8.0.13 and later does not verify TLS connections: If you use MySQL Connector/J 8.0.13 or later with MySQL for VMware Tanzu, you must modify the JDBC URL in VCAP_SERVICES to include sslMode=VERIFY_IDENTITY and verifyServerCertificate=true.
  
  For more information about JDBC URL syntax, see the MySQL documentation. For more information about VCAP_SERVICES, see MySQL Environment Variables.

• Plan 1 must be active: If you set Plan 1 to Inactive in the MySQL for VMware Tanzu tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.

Compatibility

The following components are compatible with this release:

* Components marked with an asterisk have been updated

v2.8.1

Release Date: May 21, 2020

Features

New features and changes in this release:

• Filenames for backup artifacts include an instance UUID: Operators can use this UUID to differentiate between the leader and follower backup artifacts.

• Developers can enable lowercase table names when they update service instances: If an operator selects Allow Developers To Override Lower Case Table Names in the tile, developers can enable and disable the lower_case_table_names property when they update a service instance. Previously, they could only enable this feature when they created a service instance.

Resolved Issues

This release has the following fixes:

• Smoke tests no longer fail with a timeout: Previously, if you had many buildpacks in your environment, smoke tests sometimes failed.

• Enable Lower Case Table Names no longer enables the feature on existing service instances: Previously, if a developer selected Enable Lower Case Table Names in the tile, existing tables with uppercase names were orphaned. Now, if the feature is enabled in the tile, Enable Lower Case Table Names is only applied to new service instances.

• Leader-follower backups are no longer overwritten: Previously, MySQL for VMware Tanzu sometimes only stored one backup file from a random node. Now, MySQL for VMware Tanzu uploads both the leader and follower backup artifacts to the blobstore.

Known Issues

This release has the following issues:

• Uppercase letters in the service network name blocks Multi-Site Replication setup: BOSH DNS can only resolve lowercase letters. Because the service network name is only used to reference the network configuration in BOSH, change the network name to lowercase letters.

• New service instances cannot be configured for Multi-Site Replication with TAS for VMs v2.10: This does not affect existing service instances that are already configured for Multi-Site Replication. Other service plan topologies are also unaffected.

• Multi-Site Replication is unsupported for TAS for VMs v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in TAS for VMs v2.6.

• For Ops Manager v2.6 and earlier, automated backups using SCP silently fail: For workaround instructions, see MySQL SCP backups are failing when prompting for the SSH key passphrase in PCF in the VMware Tanzu Network knowledge base.

• MySQL Connector/J 8.0.13 and later does not verify TLS connections: If you use MySQL Connector/J 8.0.13 or later with MySQL for VMware Tanzu, you must modify the JDBC URL in VCAP_SERVICES to include sslMode=VERIFY_IDENTITY and verifyServerCertificate=true.
  
  For more information about JDBC URL syntax, see the MySQL documentation. For more information about VCAP_SERVICES, see MySQL Environment Variables.

• Plan 1 must be active: If you set Plan 1 to Inactive in the MySQL for VMware Tanzu tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.

Compatibility

The following components are compatible with this release:

* Components marked with an asterisk have been updated

v2.8.0

Release Date: April 16, 2020

Features

New features and changes in this release:

Multi‑Site Replication

• Open beta for Multi‑Site Replication plans: Developers can configure a follower service instance for multi‑site replication across foundations. For more information, see Using MySQL for VMware Tanzu for Multi-Site Replication.

• Backup and restore Multi‑Site Replication service instances: Operators can configure automated backups for Multi‑Site Replication service instances. Operators can also use the mysql-restore utility to restore a Multi‑Site Replication instance from a backup. For more information, see Backing up MySQL for VMware Tanzu and Restoring MySQL for VMware Tanzu.

• Multi‑Site Replication metrics: You can view metrics for Multi‑Site Replication service instances in realtime using cf tail.

Additional New Features

• Individual service instance upgrades: Developers can upgrade MySQL for VMware Tanzu on-demand service instances individually using the Cloud Foundry Command Line Interface (cf CLI). For more information about this feature, see About Individual Service Instance Upgrades. For instructions for individually upgrading service instances, see Upgrade an Individual Service Instance.

• Telemetry data: MySQL for VMware Tanzu sends Telemetry data when the Telemetry tile is enabled in your foundation. For more information about the Telemetry tile, see Telemetry for Ops Manager.

• Operators can run the recreate-all-service-instances errand to re-create service instance VMs.

Feature Improvements

• Improved certificate rotation workflow: MySQL for VMware Tanzu is compatible with the Ops Manager CredHub Maestro certificate rotation feature. Operators can enable this feature in Ops Manager v2.8 and later. For more information, see CredHub Maestro Rotates BOSH DNS Certificate Authorities.

• Change Highly Available (HA) cluster server defaults: Developers can set optional parameters to change MySQL server defaults for HA cluster plans. For instructions for changing server defaults, see Changing Defaults Using Arbitrary Parameters.

• Restore HA Clusters with mysql-restore Utility: Operators can use the mysql-restore utility to restore an HA cluster from a backup. For more information about the mysql-restore utility, see Restore the Service Instance.

• An error message appears when developers bind apps to custom schemas with invalid names. The error message shows the valid characters for custom schema names.

• Apps no longer timeout when connecting to service instances because of latencies in BOSH DNS hostname resolution. This issue has been resolved for app and service key bindings to service instances of all plan types.

• MySQL for VMware Tanzu syslog configuration is now managed by Ops Manager. This improvement does not affect syslog configuration in the tile. However, if you use the Ops Manager API or Platform Automation Toolkit, you must modify your syslog configuration to use syslog-properties. When you modify your configuration, ensure that you use om CLI v3.2.0 or later. For more information about syslog-properties, see om in GitHub.

Security Fix

This release includes the following security update:

• Expired and unused certificates for HA clusters no longer are stored on HA cluster service instances.

Known Issues

This release has the following issues:

• Uppercase letters in the service network name blocks Multi-Site Replication setup: BOSH DNS can only resolve lowercase letters. Because the service network name is only used to reference the network configuration in BOSH, change the network name to lowercase letters.

• New service instances cannot be configured for Multi-Site Replication with TAS for VMs v2.10: This does not affect existing service instances that are already configured for Multi-Site Replication. Other service plan topologies are also unaffected.

• If you have many buildpacks in your environment, smoke tests may fail with timeout: To mitigate this issue, reduce the number of buildpacks in your environment.

• Multi-Site Replication is unsupported for TAS for VMs v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in TAS for VMs v2.6.

• Leader-follower backups are overwritten: For leader-follower automated backups, MySQL for VMware Tanzu might store only one backup file from a random node. This issue occurs because leader and follower backup files are timestamped and stored in the same location. This can cause the files to overwrite each other. For information about backup files, see Backup Files and Metadata.

• For Ops Manager v2.6 and earlier, automated backups using SCP silently fail: For workaround instructions, see MySQL SCP backups are failing when prompting for the SSH key passphrase in PCF in the VMware Tanzu Network knowledge base.

• MySQL Connector/J 8.0.13 and later does not verify TLS connections: If you use MySQL Connector/J 8.0.13 or later with MySQL for VMware Tanzu, you must modify the JDBC URL in VCAP_SERVICES to include sslMode=VERIFY_IDENTITY and verifyServerCertificate=true.
  
  For more information about JDBC URL syntax, see the MySQL documentation. For more information about VCAP_SERVICES, see MySQL Environment Variables.

• Enable Lower Case Table Names enables the feature on existing service instances: If a developer selects Enable Lower Case Table Names in the tile, the feature is automatically enabled on existing service instances. This can cause existing tables with uppercase names to become orphaned.

• Plan 1 must be active: If you set Plan 1 to Inactive in the MySQL for VMware Tanzu tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.

Compatibility

The following components are compatible with this release:

* Components marked with an asterisk have been updated

View Release Notes for Another Version

To view the release notes for another product version, select the version from dropdown at the top of this page.