Release Notes

Note: Pivotal has renamed MySQL for Pivotal Cloud Foundry to MySQL for Pivotal Platform.

Note: Pivotal has renamed Pivotal Cloud Foundry to Pivotal Platform.

Page last updated:

Pivotal 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 product versions and upgrade paths, see Upgrade Planner.

v2.7.8

Release Date: May 20, 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.

  • Broker requests no longer fail: Previously, if a developer bound a MySQL for Pivotal Platform v2.6 service instance using MySQL for Pivotal Platform v2.7, broker requests failed. In this case, developers could not bind or update service instances.

  • 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 Pivotal Platform sometimes only stored one backup file from a random node. Now, MySQL for Pivotal Platform uploads both the leader and follower backup artifacts to the blobstore.

Known Issues

This release has the following issues:

  • Multi-Site Replication is unsupported for PAS v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in PAS v2.6.
  • 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 Pivotal Platform, 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.
  • If you set Plan 1 to Inactive in the MySQL for Pivotal Platform 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
Stemcell315.183*
Percona Server5.7.28-31
Percona XtraDB Cluster5.7.28-31.41
Percona XtraBackup2.4.20*
mysql-backup-release2.14.0*
mysql-monitoring-release9.13.0*
pxc-release0.26.0*

* Components marked with an asterisk have been updated

v2.7.7

Release Date: April 8, 2020

Resolved Issues

This release has the following fixes:

  • MySQL for Pivotal Platform now configures the endpoint URL for s3 backups and does not always uses the default AWS endpoint.

Known Issues

This release has the following issues:

  • 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 PAS v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in PAS v2.6.
  • Leader-follower backups are overwritten: For leader-follower automated backups, MySQL for Pivotal Platform 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.
  • 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 Pivotal Platform, 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.
  • Broker requests fail: If a developer binds a MySQL for Pivotal Platform v2.6 service instance using MySQL for Pivotal Platform v2.7, broker requests fail. In this case, developers cannot bind or update service instances.
  • 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.
  • If you set Plan 1 to Inactive in the MySQL for Pivotal Platform 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
Stemcell315.174*
Percona Server5.7.28-31
Percona XtraDB Cluster5.7.28-31.41
Percona XtraBackup2.4.18 and 2.4.15
mysql-backup-release2.13.0
mysql-monitoring-release9.11.0
pxc-release0.24.0*

* Components marked with an asterisk have been updated

v2.7.6

Release Date: February 24, 2020

Features

New features and changes in this release:

  • Operators can monitor Key Performance Indicators (KPIs) for persistent and ephemeral disk usage, and number of connections on the Healthwatch Indicator Protocol dashboard. For more information, see Use the Indicator Protocol Dashboard.

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

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

Resolved Issues

This release has the following fixes:

  • An inaccurate generic message no longer appears when you use cf update-service to migrate data between a highly available (HA) cluster plan and a plan of another topology. MySQL for Pivotal Platform now fails fast to indicate that this is an unsupported workflow.

  • For Ops Manager v2.7 and later, automated backups using SCP no longer silently fail.

Known Issues

This release has the following issues:

  • 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 PAS v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in PAS v2.6.
  • Backups do not upload to s3 external storage: MySQL for Pivotal Platform does not configure the endpoint url and instead uses the default AWS endpoint.

    This issue impacts:

    • Amazon S3 buckets that use custom endpoints
    • Ceph storage clusters
    • Other S3-compatible endpoints certified by VMware

    To mitigate this issue, configure a different external storage option. You can configure secure copy protocol (SCP), Google Cloud Storage (GCS), or Azure Storage. For more information about how to configure external storage, see About Configuring Automated Backups.

  • Leader-follower backups are overwritten: For leader-follower automated backups, MySQL for Pivotal Platform 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.
  • 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 Pivotal Platform, 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.
  • Broker requests fail: If a developer binds a MySQL for Pivotal Platform v2.6 service instance using MySQL for Pivotal Platform v2.7, broker requests fail. In this case, developers cannot bind or update service instances.
  • 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.
  • If you set Plan 1 to Inactive in the MySQL for Pivotal Platform 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
Stemcell315.183*
Percona Server5.7.28-31
Percona XtraDB Cluster5.7.28-31.41
Percona XtraBackup2.4.18 and 2.4.15
mysql-backup-release2.13.0*
mysql-monitoring-release9.11.0*
pxc-release0.22.0

* Components marked with an asterisk have been updated

v2.7.5

Release Date: January 21, 2020

Security Fixes

This release includes the following security fix:

  • Updates all dependencies to golang v1.13. This fixes the following CVE:

Resolved Issue

This release has the following fix:

  • An inaccurate generic message no longer appears when the MySQL service broker fails to connect to the MySQL server.

Known Issues

This release has the following issues:

  • 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 PAS v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in PAS v2.6.
  • Backups do not upload to s3 external storage: MySQL for Pivotal Platform does not configure the endpoint url and instead uses the default AWS endpoint.

    This issue impacts:

    • Amazon S3 buckets that use custom endpoints
    • Ceph storage clusters
    • Other S3-compatible endpoints certified by VMware

    To mitigate this issue, configure a different external storage option. You can configure secure copy protocol (SCP), Google Cloud Storage (GCS), or Azure Storage. For more information about how to configure external storage, see About Configuring Automated Backups.

  • Leader-follower backups are overwritten: For leader-follower automated backups, MySQL for Pivotal Platform 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.
  • An inaccurate generic message appears when you use cf update-service to migrate data between a highly available (HA) cluster plan and a plan of another topology.
  • 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 Pivotal Platform, 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.
  • Broker requests fail: If a developer binds a MySQL for Pivotal Platform v2.6 service instance using MySQL for Pivotal Platform v2.7, broker requests fail. In this case, developers cannot bind or update service instances.
  • 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.
  • If you set Plan 1 to Inactive in the MySQL for Pivotal Platform 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
Stemcell315.154*
Percona Server5.7.28-31
Percona XtraDB Cluster5.7.28-31.41
Percona XtraBackup2.4.18 and 2.4.15
mysql-backup-release2.12.0
mysql-monitoring-release9.9.0
pxc-release0.22.0

* Components marked with an asterisk have been updated

v2.7.4

Release Date: January 6, 2020

Features

New features and changes in this release:

  • Multi‑Site Replication plans support failover to a follower service instance in a different data center.

    Note: Multi‑Site Replication plans are currently in beta. If you discover any bugs, contact Support.

  • Operators can monitor MySQL metrics on the Healthwatch Indicator Protocol dashboard. For more information, see Use the Indicator Protocol Dashboard.

  • Highly available (HA) cluster plans only retain three days of binary logs. This reduces persistent disk usage.

Security Fixes

This release includes the following security fixes:

Resolved Issues

This release has the following fixes:

  • Single node service instances no longer emit metrics for leader-follower service instances.
  • Smoke test error messages now explain the actual error rather than outputting fork/exec /usr/local/bin/bosh: no such file or directory.
  • Audit logs are now stored on the persistent disk rather than on the syslog endpoint.

Known Issues

This release has the following issues:

  • 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 PAS v2.5 and earlier: Multi-Site Replication requires Cloud Foundry API (CAPI) v3 as a dependency, which is introduced in PAS v2.6.
  • Leader-follower backups are overwritten: For leader-follower automated backups, MySQL for Pivotal Platform 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.
  • An inaccurate generic message appears when the MySQL service broker fails to connect to the MySQL server.
  • An inaccurate generic message appears when you use cf update-service to migrate data between a highly available (HA) cluster plan and a plan of another topology.
  • 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 Pivotal Platform, 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.
  • Broker requests fail: If a developer binds a MySQL for Pivotal Platform v2.6 service instance using MySQL for Pivotal Platform v2.7, broker requests fail. In this case, developers cannot bind or update service instances.
  • 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.
  • If you set Plan 1 to Inactive in the MySQL for Pivotal Platform 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
Stemcell315.146*
Percona Server5.7.28-31*
Percona XtraDB Cluster5.7.28-31.41*
Percona XtraBackup2.4.18 and 2.4.15*
mysql-backup-release2.12.0*
mysql-monitoring-release9.9.0*
pxc-release0.22.0*

* Components marked with an asterisk have been updated

v2.7.2

Release Date: October 21, 2019

Features

New features and changes in this release:

  • MySQL for Pivotal Platform supports a beta Multi‑Site Replication service plan. This plan has the following features:

    • Replication across two routable Pivotal Application Service foundations secured over mTLS. The primary node in a foundation only trusts the secondary node in another foundation.
    • The ability to bind and push apps to a primary node in a foundation and a secondary node in another foundation.

      Note: Multi‑Site Replication plans are currently in beta. If you discover any bugs, contact Support.

  • Highly available (HA) cluster plans are now in general availability (GA).

  • Updates Percona Server to v5.7.26-29.

  • Updates pxc-release to v0.20.0.

  • Updates Envoy to v1.11.1.

Security Fix

This release includes the following security fix:

  • Updates bpm-release to v1.1.3. This update fixes Medium CVE-2019-9893.

Resolved Issues

This release has the following fixes:

  • Smoke tests no longer fail when TLS is not configured.
  • You can now share MySQL for Pivotal Platform service instances across orgs and spaces using cf share-service. For more information, see Share Service Instances.
  • Certificate rotation now works reliably with BOSH.

Known Issues

This release has the following issues:

  • 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.
  • Leader-follower backups are overwritten: For leader-follower automated backups, MySQL for Pivotal Platform 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.
  • An inaccurate generic message appears when the MySQL service broker fails to connect to the MySQL server.
  • An inaccurate generic message appears when you use cf update-service to migrate data between a highly available (HA) cluster plan and a plan of another topology.
  • Smoke test error messages do not explain the actual error and output the following message instead fork/exec /usr/local/bin/bosh: no such file or directory.
  • Single node service instances emit metrics for leader-follower service instances.
  • Audit logs are stored on the syslog endpoint rather than on the persistent disk.
  • 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 Pivotal Platform, 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.
  • Broker requests fail: If a developer binds a MySQL for Pivotal Platform v2.6 service instance using MySQL for Pivotal Platform v2.7, broker requests fail. In this case, developers cannot bind or update service instances.
  • 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.
  • If you set Plan 1 to Inactive in the MySQL for Pivotal Platform 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
Stemcell315.103*
Percona Server5.7.26-29
Percona XtraDB Cluster5.7.26-31.37
Percona XtraBackup2.4.15 and 2.4.8
mysql-backup-release2.11.0
mysql-monitoring-release9.6.0
pxc-release0.20.0

* Components marked with an asterisk have been updated

v2.7.1 - Withdrawn

Release Date: October 10, 2019

This release has been removed from Pivotal Network because of an issue that occurs when TLS is not configured.

Features

New features and changes in this release:

  • MySQL for Pivotal Platform supports a beta Multi‑Site Replication service plan. This plan has the following features:

    • Replication across two routable Pivotal Application Service foundations secured over mTLS. The primary node in a foundation only trusts the secondary node in another foundation.
    • The ability to bind and push apps to a primary node in a foundation and a secondary node in another foundation.

      Note: Multi‑Site Replication plans are currently in beta. If you discover any bugs, contact Support.

  • Highly available (HA) cluster plans are now in general availability (GA).

  • Updates Percona Server to v5.7.26-29.

  • Updates pxc-release to v0.20.0.

  • Updates Envoy to v1.11.1.

Security Fix

This release includes the following security fix:

  • Updates bpm-release to v1.1.3. This update fixes Medium CVE-2019-9893.

Resolved Issues

This release has the following fixes:

  • You can now share MySQL for Pivotal Platform service instances across orgs and spaces using cf share-service. For more information, see Share Service Instances.
  • Certificate rotation now works reliably with BOSH.

Known Issues

This release has the following issues:

  • 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.
  • Leader-follower backups are overwritten: For leader-follower automated backups, MySQL for Pivotal Platform 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.
  • An inaccurate generic message appears when the MySQL service broker fails to connect to the MySQL server.
  • An inaccurate generic message appears when you use cf update-service to migrate data between a highly available (HA) cluster plan and a plan of another topology.
  • Smoke test error messages do not explain the actual error and output the following message instead fork/exec /usr/local/bin/bosh: no such file or directory.
  • Single node service instances emit metrics for leader-follower service instances.
  • Audit logs are stored on the syslog endpoint rather than on the persistent disk.
  • 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 Pivotal Platform, 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.
  • Broker requests fail: If a developer binds a MySQL for Pivotal Platform v2.6 service instance using MySQL for Pivotal Platform v2.7, broker requests fail. In this case, developers cannot bind or update service instances.
  • 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.
  • If you set Plan 1 to Inactive in the MySQL for Pivotal Platform tile, your installation fails when you apply changes. To fix this issue, ensure that Plan 1 is always configured.
  • Smoke tests fail when TLS is not configured.

Compatibility

The following components are compatible with this release:

Component Version
Stemcell315.99*
Percona Server5.7.26-29
Percona XtraDB Cluster5.7.26-31.37
Percona XtraBackup2.4.15 and 2.4.8*
mysql-backup-release2.11.0
mysql-monitoring-release9.6.0
pxc-release0.20.0*

* Components marked with an asterisk have been updated

v2.7.0

Release Date: August 7, 2019

Features

New features and changes in this release:

  • When you upgrade to MySQL for Pivotal Platform v2.7, MySQL for Pivotal Platform automatically rotates internal certificates and certificate authority (CA) certificates. The new certificates do not expire for 5 years. For more information, see Managing Certificates.

  • Automatic backups are now compatible with the AWS CLI v1.16.189, which defaults to Amazon S3 Signature Version 4 for S3 buckets when no other configuration is provided.

Security Fix

This release includes the following security fix:

  • Updates the cf CLI to v6.46

Known Issues

This release has the following issues:

  • 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.
  • Leader-follower backups are overwritten: For leader-follower automated backups, MySQL for Pivotal Platform 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.
  • You cannot share MySQL for Pivotal Platform service instances across orgs and spaces. If you run cf share-services, the command fails.
  • An inaccurate generic message appears when the MySQL service broker fails to connect to the MySQL server.
  • An inaccurate generic message appears when you use cf update-service to migrate data between a highly available (HA) cluster plan and a plan of another topology.
  • Smoke test error messages do not explain the actual error and output the following message instead fork/exec /usr/local/bin/bosh: no such file or directory.
  • Single node service instances emit metrics for leader-follower service instances.
  • Audit logs are stored on the syslog endpoint rather than on the persistent disk.
  • 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 Pivotal Platform, 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.
  • Broker requests fail: If a developer binds a MySQL for Pivotal Platform v2.6 service instance using MySQL for Pivotal Platform v2.7, broker requests fail. In this case, developers cannot bind or update service instances.
  • 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.
  • If you set Plan 1 to Inactive in the MySQL for Pivotal Platform 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
Stemcell315.70
Percona Server5.7.26-29
Percona XtraDB Cluster5.7.26-31.37
Percona XtraBackup2.4.12 and 2.4.8
mysql-backup-release2.11.0
mysql-monitoring-release9.6.0
pxc-release0.19.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.