Release Notes

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 example, if you use an older v2.5 .x version, upgrade to the latest v2.5.x version before upgrading to the latest v2.6.x version.

For product versions and upgrade paths, see Upgrade Planner.

v2.6.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.

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.

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

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

v2.6.7

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

v2.6.6

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 Issues

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

v2.6.5

Release Date: January 7, 2020

Features

New features and changes in this release:

  • Operators can monitor MySQL metrics on the Healthwatch Indicator Protocol dashboard. For more information, see Indicator Protocol Dashboard (Beta).
  • 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:

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

v2.6.4

Release Date: Oct 10, 2019

Security Fix

This release includes the following security fix:

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

Feature

New feature and change in this release:

  • Updates pxc-release to 0.20.0.

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

v2.6.3

Release Date: Aug 20, 2019

Security Fix

This release includes the following security fix:

Feature

New feature and change in this release:

  • Updates Percona Server to v5.7.26-29.

Resolved Issue

This release has the following fix:

  • Automatic backups for leader-follower service instances now work correctly. Previously, a regression caused the leader or follower node to take a backup of its peer node rather than itself.

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

v2.6.2

Release Date: July 19, 2019

Features

New features and changes in this release:

  • MySQL for PCF v2.6.2 updates the global service instance limit to 500 instances.
  • Better error messaging when attempting to do cf bind-service on a service instances that is on an older version than the MySQL service broker.
  • Renames Galera [BETA] service plan type to HA Cluster [BETA].
  • Updates the service instance limit for highly available (HA) cluster service plan types to 50 instances.
  • Updates AWS CLI version used by automatic backups to support non-public AWS regions and external object stores that require the v4 signature.
  • Enables developers to bind their app to a custom schema in the database. For more information, see Use Custom Schemas.
  • Updates Golang version to v1.12.

Resolved Issue

This release has the following fix:

  • Fixes bug where the smoke tests CF app respects the apps_domain configured in the PAS tile.

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

v2.6.1

This patch version was never released. Upgrade directly to MySQL for PCF v2.6.2 or later.

v2.6.0

Release Date: June 19, 2019

Features

New features and changes in this release:

  • When you upgrade to MySQL for PCF v2.6, MySQL for PCF automatically rotates internal certificates for single node and leader-follower service instances. The new certificates do not expire for 5 years. MySQL for PCF does not automatically rotate TLS certificates or certificates for HA cluster service instances during upgrades. For more information, see Rotating Certificates.

    Warning: If your internal certificates expire, service bindings and backups fail.

  • HA cluster plans are compatible with plugins for Encryption at Rest.

  • Handling is improved for empty data directories on initialization.

  • MySQL for PCF relies significantly more on bpm (BOSH Process Manager) for how it launches jobs. For general information about bpm, see bpm in the BOSH documentation.

  • New MySQL property configurations improve performance of HA cluster plans.

  • The Percona Server version is updated to v5.7.24-26.

  • The golang version is updated to v1.12.x.

Resolved Issues

This release has the following fixes:

  • Java apps can use HA cluster plans with or without enabling TLS.

  • Internal diagnostic and backup components of HA cluster plans make troubleshooting easier and more accurate.

  • The drain script no longer times out.

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

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.