This site will be decommissioned on January 30th 2025. After that date content will be available at techdocs.broadcom.com.

 

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

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 VMware SQL with MySQL for Tanzu Application Service containing that patch.

Important

VMware SQL with MySQL for Tanzu Application Service 3.0 introduces support for MySQL 8.0. For more information about the upgrade process from 5.7 to 8.0, including items to review to ensure a smooth transition, please see Upgrading from MySQL 5.7 to 8.0.

v3.0.7

Release Date: April 8th, 2024

Changes

This release includes the following changes:

  • When you configure an inactive plan, the MySQL Default Version text box for the plan is set to MySQL 8.0 by default, instead of the previous default value MySQL 5.7.
  • The bootstrap errand now self-selects a high-availability cluster instance node on which to run, and no longer requires the --instance flag.
  • A number of high and critical CVEs are addressed by updating components to the latest version.

Resolved Issues

This release resolves the following issues:

  • Binding creation is further isolated from ongoing transaction execution. Previously, binding creation during an active transaction sometimes failed or aborted the transaction.
  • Improved recovery of MySQL service instances after a VM reboot.
  • The bootstrap errand now self-selects a high-availability cluster instance node on which to run, and no longer requires the --instance flag.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 1.406*
Percona Server 5.7.44-48
Percona Server 8.0.36-28*
Percona XtraDB Cluster 5.7.44-31.65
Percona XtraDB Cluster 8.0.36-28*
Percona XtraBackup 2.4.29
Percona XtraBackup 8.0.35-30
adbr-release 0.103.0*
bpm-release 1.2.18*
cf-cli-release 1.59.0
cf-service-gateway-release 148.0.0*
count-cores-indicator-release 2.0.0
dedicated-mysql-release 0.187.66*
dedicated-mysql-adapter-release 0.340.74*
loggregator-agent-release 7.7.5*
mysql-data-backup-restore-release 3.1.0*
mysql-monitoring-release 10.13.0*
on-demand-service-broker-release 0.45.4*
pxc-release 1.0.26*
routing-release 0.295.0*
service-metrics-release 2.0.36*

v3.0.6

Release Date: Jan 19th, 2024

Changes

This release includes the following changes:

  • A number of high and critical CVEs were addressed by updating the components to the latest version

Resolved Issues

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 1.340*
Percona Server 8.0.34-26*
Percona Server 5.7.42-46
Percona XtraDB cluster 8.0.35-27*
Percona XtraDB cluster 5.7.44-48*
Percona XtraBackup 8.0.35-30*
Percona XtraBackup 2.4.29*
adbr-release 0.98.0*
bpm-release 1.2.13*
cf-cli-release 1.59.0*
cf-service-gateway-release 140.0.0*
count-cores-indicator-release 2.0.0*
dedicated-mysql-release 0.187.48*
dedicated-mysql-adapter-release 0.340.55*
loggregator-agent-release 7.7.4*
mysql-backup-release 2.37.0*
mysql-monitoring-release 10.10.0*
on-demand-service-broker-release 0.45.3*
pxc-release 1.0.23*
routing-release 0.287.0*
service-metrics-release 2.0.34*

v3.0.5

This version was an internal dev-release

v3.0.4

Release Date: Oct 24th, 2023

Changes

This release includes the following changes:

  • A number of high and critical CVEs were addressed by updating the components to the latest version

Resolved Issues

This release resolves the following issues: + Smoke tests could fail when service instance creation takes longer than 10 minutes. This was a regression introduced in MySQL v3.0.2. The previous service instance creation timeout of 60 minutes has been restored.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 1.260*
Percona server 8.0.33-25
Percona server 5.7.42-46
Percona xtraDB cluster 8.0.33-25
Percona xztraDB cluster 5.7.42-31.65
Percona xtraBackup 8.0.33-28
Percona xtraBackup 2.4.28
adbr-release 0.93.0*
bpm-release 1.2.9*
cf-cli-release 1.50.0*
cf-service-gateway-release 128.0.0*
count-cores-indicator-release 2.0.0
dedicated-mysql-release 0.187.27*
dedicated-mysql-adapter-release 0.340.35*
loggregator-agent-release 7.6.4*
mysql-backup-release 2.32.0*
mysql-monitoring-release 10.5.0*
on-demand-service-broker-release 0.45.0*
pxc-release 1.0.18*
routing-release 0.283.0*
service-metrics-release 2.0.33*

v3.0.3

This version was an internal dev-release

v3.0.2

Release Date: Sep 12th, 2023

Resolved Issues

This release resolves the following issues:

  • MySQL service bindings support MariaDB Connector/J v3.0 and later::

    MariaDB Connector/J 3.0 and later, by default, accept only jdbc:mariadb connection strings.

    In service bindings created by the MySQL tile, the jdbcUrl parameter now includes the permitMysqlScheme option. This ensures that apps that use MariaDB Connector/J 3.0 and later are compatible with MySQL tile service bindings.

  • Percona 8.0.22: DROP USER fails with an error if any account to be dropped is named as the DEFINER attribute for any stored object.::

    This release addresses this breaking change in Percona. Deleting a service key no longer results in a failure when the user associated with the service key has been used to create stored objects. Instead, as in previous releases, the objects will be orphaned.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 1.222*
Stemcell 1.232*
Percona server 5.7.43-47*
Percona server 8.0.33-25*
Percona server 5.7.42-46
Percona xtraDB Cluster 8.0.33-25*
Percona xtraDB Cluster 5.7.42-31.65*
Percona xtraBackup 8.0.33-28*
Percona xtraBackup 2.4.28
adbr-release 0.88.0*
bpm-release 1.2.7*
cf-cli-release 1.47.0*
cf-service-gateway-release 123.0.0*
count-cores-indicator-release 2.0.0
dedicated-mysql-release 0.187.20*
dedicated-mysql-adapter-release 0.340.24*
loggregator-agent-release 7.6.2*
mysql-backup-release 2.31.0*
mysql-monitoring-release 10.4.0*
on-demand-service-broker-release 0.43.3*
pxc-release 1.0.17*
routing-release 0.280.0*
service-metrics-release 2.0.32*

* Components marked with an asterisk have been updated

v3.0.1

Release Date: Jul 20th, 2023

Changes

This release includes the following changes:

  • A number of high and critical CVEs were addressed by updating the components to the latest version
  • Customers who are enrolled to capture telemetry can additionally track the number of CPU cores consumed by all MySQL service instances within a foundation

Known Issues

This release has the following known issues:

There is a known issue as of Percona 8.0.22: DROP USER fails with an error if any account to be dropped is named as the DEFINER attribute for any stored object. This error can occur if a service binding user creates a stored object (EVENTS, ROUTINES, TRIGGERS or VIEWS) and a delete of the service binding is attempted.

The following steps result in this error:

Connect to DB using credentials from the service key and create a stored object, then delete the service key.

cf create-service-key DB DB-KEY
cf delete-service-key DB DB-KEY

This causes the error:

Deleting key DB-KEY for service instance DB as admin...
FAILED
Server error, status code: 502, error code: 10001, message: Service broker failed to delete service binding for instance smallDb8: Service broker error: There was a problem completing your request. Please contact your operations team providing the following information: service: p.mysql, service-instance-guid: GUID, broker-request-id: ID, operation: unbind

This fails because the DROP USER command would result in the creation of an orphaned stored object. To avoid this error, first drop the associated stored objects or redefine them to have a different definer.

MySQL documentation for orphaned objects

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 1.148
Percona server 8.0.32-24*
Percona server 5.7.42-46
Percona xtraDB Cluster 8.0.32-24*
Percona xtraDB Cluster 5.7.41-31.65*
Percona xtraBackup 8.0.32-26*
Percona xtraBackup 2.4.28
adbr-release 0.83.0*
bpm-release 1.2.4*
cf-cli-release 1.45.0*
cf-service-gateway-release 114.0.0*
count-cores-indicator-release 2.0.0*
dedicated-mysql-release 0.187.14*
dedicated-mysql-adapter-release 0.340.12*
loggregator-agent-release 6.5.12*
mysql-backup-release 2.27.0*
mysql-monitoring-release 10.1.0*
on-demand-service-broker-release 0.43.2*
pxc-release 1.0.14*
routing-release 0.275.0*
service-metrics-release 2.0.30*

v3.0.0

Release Date: April 5th, 2023

Changes

This release includes the following changes:

  • Support for MySQL 5.7 and 8.0: a new MySQL Default Version field for service plans enables operators to select either MySQL 5.7 or MySQL 8.0 as the default version for service instances created using the plan.
  • The tile requires Ubuntu Jammy stemcell 1.95 or later.
  • The number of available service plans has increased from 9 to 18.
  • For HA service instances, all nodes use TLS for internal communication.
  • VM extensions: a new field for service plans enables operators to configure a list of custom VM extensions that apply to VMs for service instances created using the plan.

Breaking Changes

This release includes the following breaking changes:

  • The enable_tls property has been renamed to enforce_client_tls.
  • Ubuntu Jammy stemcells require TLS v1.2 or above.
  • MySQL 8.0 service instances support both TLS v1.2 and TLS v1.3. MySQL 5.7 service instances support only TLS v1.2.

Known Issues

This release has the following known issues:

There is a known issue as of Percona 8.0.22: DROP USER fails with an error if any account to be dropped is named as the DEFINER attribute for any stored object. This error can occur if a service binding user creates a stored object (EVENTS, ROUTINES, TRIGGERS or VIEWS) and a delete of the service binding is attempted.

The following steps result in this error:

Connect to DB using credentials from the service key and create a stored object, then delete the service key.

cf create-service-key DB DB-KEY
cf delete-service-key DB DB-KEY

This causes the error:

Deleting key DB-KEY for service instance DB as admin...
FAILED
Server error, status code: 502, error code: 10001, message: Service broker failed to delete service binding for instance smallDb8: Service broker error: There was a problem completing your request. Please contact your operations team providing the following information: service: p.mysql, service-instance-guid: GUID, broker-request-id: ID, operation: unbind

This fails because the DROP USER command would result in the creation of an orphaned stored object. To avoid this error, first drop the associated stored objects or redefine them to have a different definer.

MySQL documentation for orphaned objects

Compatibility

The following components are compatible with this release:

Component Version
Stemcell 1.95
Percona server 8.0.31-23*
Percona server 5.7.40-43
Percona xtraDB Cluster 8.0.31-23*
Percona xtraDB Cluster 5.7.40-31.63
Percona xtraBackup 8.0.32-25*
Percona xtraBackup 2.4.27
pxc-release 1.0.8*
mysql-backup-release 2.25.0*
mysql-monitoring-release 9.24.0*
dedicated-mysql-release 0.187.0*

* Components marked with an asterisk have been updated

check-circle-line exclamation-circle-line close-line
Scroll to top icon