Release Notes

Page last updated:

VMware recommends that you upgrade to the latest patch for your current minor, and then upgrade to the latest available patch for the next minor.

For product versions and upgrade paths, see Upgrade Planner.

Because VMware uses the Percona Distribution for MySQL, expect a time lag between Oracle releasing a MySQL patch and VMware releasing Tanzu SQL with MySQL for VMs containing that patch.

v2.10.5

Release Date: October 14, 2021

Features

This release has the following new feature:

  • Added custom tags for on-demand MySQL service instance VMs:

There is a new field in the MySQL tile Settings page for tags that apply to the Cloud Provider. The accepted format depends on the underlying Cloud Provider. For example, Google Cloud Platform does not allow uppercase characters.

Resolved Issues

This release has the following fixes:

  • Fixed incompatibility with stemcell v621.141: Incompatibility with stemcell v621.141 interfered with two processes:
    • The restore procedure that makes API calls to monit to stop, start, or restart the MySQL process.
    • The bootstrap errand that recovers an HA cluster that has lost quorum.
  • Backups larger that 50 GB now succeed: There was a known issue of backups larger than 50 GB failing to complete. Backups can now be as large as 1000 GB.

Known Issues

This release has the following issue:

  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs 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:

Component Version
Stemcell621.141*
Percona Server5.7.34–37
Percona XtraDB Cluster5.7.34–31.51
Percona XtraBackup2.4.23
mysql-backup-release2.17.0
mysql-monitoring-release9.15.0
pxc-release0.37.0

* Components marked with an asterisk have been updated

v2.10.4

Release Date: August 17, 2021

Security Fixes

This release includes the following security fix:

  • On Multi-Site Replication instances, the admin port on service instances has been removed: Now, Envoy only listens on the MySQL port, and multi-site instances do not have any externally available admin interfaces.

Resolved Issues

This release has the following fixes:

  • ApplicationDataBackupRestore (adbr) processes running on the service instances only accept TLS v1.2 connections: Previously, these adbr processes accepted all TLS connections, regardless of version.

  • Smoke test errands no longer leave orphan routes: Do a one-time cleanup of orphan routes from earlier versions of Tanzu SQL with MySQL for VMs by running:

    cf target -o system -s pivotal-services
    cf delete-orphaned-routes
    

Known Issues

This release has the following issues:

  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.
  • Stemcells v621.141 and later are not compatible with this release. To mitigate this issue, use a stemcell version between 621.136 and the minimum version indicated in the Compatibility table below.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell621.135*
Percona Server5.7.34–37*
Percona XtraDB Cluster5.7.34–31.51*
Percona XtraBackup2.4.23*
mysql-backup-release2.17.0*
mysql-monitoring-release9.15.0
pxc-release0.37.0*

* Components marked with an asterisk have been updated

v2.10.3

Release Date: May 28, 2021

Features

New feature in this release:

  • List as many backups as needed: Previously, the ApplicationDeveloperBackupRestore (adbr) plugin always listed the five most recent backups.

    Now, the adbr plugin accepts an integer parameter to specify how many backups to list. The plugin continues to list five backups by default.

    To install the new plugin, see ApplicationDataBackupRestore on the Cloud Foundry Community cf CLI Plugins website. For how to use the new limit parameter, see Procedure to Restore a Service Instance in Backing Up and Restoring.

  • Configure backup location with bucket path: The tile now accepts an optional field for bucket path. This allows backups to be stored with a path like: p.mysql > BUCKET-PATH > service-instance_GUID > yyyy > mm > dd.

    Previously, the ApplicationDeveloperBackupRestore (adbr) feature stored backup artifacts with a path like: p.mysql > service-instance_GUID > yyyy > mm > dd.

    Existing backup artifacts can still be accessed through the cf CLI using the adbr plugin.

    To configure a bucket path, follow the procedure for your external storage solution in Configuring Automated Backups.

Resolved Issues

This release has the following fix:

  • ApplicationDataBackupRestore (adbr) processes running on the service broker only accept TLS v1.2 connections: Previously, these adbr processes accepted all TLS connections, regardless of version.

Known Issues

This release has the following issues:

  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.
  • Stemcells v621.141 and later are not compatible with this release. To mitigate this issue, use a stemcell version between 621.136 and the minimum version indicated in the Compatibility table below.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell621.125*
Percona Server5.7.33–36*
Percona XtraDB Cluster5.7.33–33*
Percona XtraBackup2.4.21
mysql-backup-release2.16.0
mysql-monitoring-release9.15.0
pxc-release0.34.0*

* Components marked with an asterisk have been updated

v2.10.2

Release Date: March 11, 2021

Features

New features and changes in this release:

  • Support Instance Profiles for backups to S3: Tanzu SQL for VMs now supports using instance profiles for backups to Amazon S3.
    This is enabled by a radio button on the Backups pane of the VMware Tanzu SQL with MySQL for VMs tile. Configuring the fields under this option allows for backups to Amazon S3 without using static credentials. For more information, see Back Up to Amazon S3 with Instance Profile.

  • Avoid filling up the Persistent Disk with Binary Logs: A checkbox restricts the space that binary logs can use on the persistent disk. For databases with a high transaction rate, this change prevents database failures due to the disk running out of space. For more information, see Limit binary log disk use to 33% of disk capacity in Installing and Configuring.

Resolved Issues

This release has the following fix:

  • ADBR does not show error “Status during Restore Operation”: Previously, the ADBR plugin showed an error status during a restore when the database was unavailable. Now, the ADBR plugin reports the restore status as being in progress.

Known Issues

This release has the following issues:

  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.
  • Stemcells v621.141 and later are not compatible with this release. To mitigate this issue, use a stemcell version between 621.136 and the minimum version indicated in the Compatibility table below.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell621.101*
Percona Server5.7.32–35*
Percona XtraDB Cluster5.7.32–31*
Percona XtraBackup2.4.21*
mysql-backup-release2.16.0*
mysql-monitoring-release9.15.0
pxc-release0.33.0

* Components marked with an asterisk have been updated

v2.10.1

Release Date: February 4, 2021

Resolved Issues

This release has the following fix:

  • Correctly enforce TLS v1.2: Previously, operators could not disable TLS v1.2 using the tile. Now, operators can upgrade all service instances to disable TLS v1.2 based on the tile configuration.

    This fix resolves the breaking change issue in v2.10.0. See v2.10.0.

Known Issues

This release has the following issues:

  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.
  • During restore, the ADBR plugin incorrectly indicates the database is unavailable: The plugin should report that the restore is in progress.
  • Stemcells v621.141 and later are not compatible with this release. To mitigate this issue, use a stemcell version between 621.136 and the minimum version indicated in the Compatibility table below.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell621.95*
Percona Server5.7.31–34
Percona XtraDB Cluster5.7.31–34
Percona XtraBackup2.4.20
mysql-backup-release2.15.0
mysql-monitoring-release9.15.0
pxc-release0.31.0

* Components marked with an asterisk have been updated

v2.10.0

Release Date: December 8, 2020

Breaking Change: Before you upgrade to VMware Tanzu SQL with MySQL for VMs v2.10, ensure that your apps support connecting to the MySQL database using TLS v1.2. This might require updating the MySQL connector. For example, if you are using MySQL Connector/J, use MySQL Connector/J v8.0.8 or later or v5.1.44 or later.

Features

New features and changes in this release:

  • External access to the MySQL database through Service-Gateway: By enabling service-gateway access, operators and developers can allow MySQL service instances to be accessed from outside VMware Tanzu Application Service for VMs platform. For more information, see About Service-Gateway Access.

  • Option to restrict MySQL client connections to TLS v1.2: When TLS is enabled, operators can choose to enforce TLS v1.2 as the minimum TLS version for client connections. Connections that use the TLS v1.1 protocol or older are then rejected by the MySQL server. For more information, see Configure TLS in Installing and Configuring.

  • Backup artifacts are organized under subfolders in external storage: Previously, the Application Developer Backup and Restore (ADBR) feature stored backup artifacts in the root directory in external storage. For easier navigation, backup artifacts are now stored under p.mysql > service-instance_GUID > yyyy > mm > dd. Old backup artifacts stored in the root directory can still be accessed through the cf CLI using the adbr plugin.

  • 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.9.1.

  • Percona Server: Upgraded to v5.7.31–34.

  • Percona XtraDB Cluster: Upgraded to v5.7.31–34.

Known Issues

This release has the following issues:

  • Plan 1 must be active: If you set Plan 1 to Inactive in the VMware Tanzu SQL with MySQL for VMs tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.
  • During restore, the ADBR plugin incorrectly indicates the database is unavailable: The plugin should report that the restore is in progress.
  • Stemcells v621.141 and later are not compatible with this release. To mitigate this issue, use a stemcell version between 621.136 and the minimum version indicated in the Compatibility table below.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell621.93*
Percona Server5.7.31–34
Percona XtraDB Cluster5.7.31–34
Percona XtraBackup2.4.20
mysql-backup-release2.15.0
mysql-monitoring-release9.15.0
pxc-release0.31.0*

* 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.