Release notes#
Learn about new features, enhancements, known issues, resolved issues, and other important details about Rackspace Cloud Databases API 1 service in the following release note information.
Note
For information about using the API, see the documentation overview.
v3.17.0, November 6, 2024#
What’s new#
Monitoring status was improved for situation when monitoring agent pid file does not exist.
Request to build MySQL 8.0 instance using a MySQL 5.6 backup will be rejected.
Backups for customers with MariaDB 10.4 replicated setups or HA groups are now created using a replica.
After a successful upgrade of an instance with a customer configuration attached, the upgraded instance will now have a new configuration attached based on the datastore version of the upgraded instance.
Encrypted backups based on original encryption functionality can now be used to create an instance based on the new encryption functionality.
Resolved issues#
Setting configuration parameter to empty value for Percona instances will no longer prevent mysql server from starting.
Using the default time zone configuration parameter for an instance will no longer prevent upgrade from succeeding.
The value for sql_mode can now contain all available settings.
Granting access to databases with period in name no longer results in a failure.
Known issues#
None
v3.16.1, March 30, 2022#
What’s new#
None for this release
Resolved issues#
Corrected issue where the delay waiting for the database server to start during an upgrade was too short and resulted in a failed updgrade.
Known issues#
None for this release
v3.16.0, March 16, 2022#
What’s new#
Eliminated downtime during backup phase of upgrades for single instances and HA groups.
Resolved issues#
MySQL connector drivers, like Google Data Studio, should no longer fail trying to connect to MariaDB 10.4/10.4enc databases.
Disk resizes for large volumes should no longer timeout after 2 minutes
Upgrade of single instance should no longer fail if instance to be upgraded has replication configuration that was not cleaned up upon detach
Upgraded replicas will now have appropriate RAM and volume for the new datastore version
Known issues#
None for this release
v3.15.0, October 27, 2021#
What’s new#
Percona version 8.0 is available for instance and HA group provisioning.
Resolved issues#
Corrected issue where tmp_disk_table_size was not available for configuring MariaDB 10.4enc instances.
Corrected issue where configuration parameter could not be assigned an empty value
Corrected issue where backups of HA groups could not be used to build an instance
Known issues#
None for this release
v3.14.0, September 22, 2021#
What’s new#
Reduced the amount of time to complete upgrades.
MySQL 5.7.34 will be installed when creating new instances of MySQL 5.7.
Resolved issues#
Corrected issue where customer users with grants on performance schema tables caused upgrades to fail.
Known issues#
None for this release
v3.13.0, July 28, 2021#
What’s new#
Max volume size has been increased from 1Tb to 1.5Tb in IAD, DFW, ORD, and LON.
Resolved issues#
Corrected issues with single instance and HA group upgrades.
Known issues#
None for this release
v3.12.0, May 4, 2021#
What’s new#
Configuration ID is displayed when showing details of an HA Group.
Listing flavors includes additional details for each flavor.
Resolved issues#
None for this release
Known issues#
None for this release
v3.11.0, February 2, 2021#
What’s new#
Backup ID can be specified when creating a replica of a single instance.
Resolved issues#
HA upgrades should no longer fail for MariaDB 10/10.1 HA groups.
Replica monitoring for Percona 5.7 should no longer report an issue with libmysqlclient_r.
Failures during resize should result in the instance going into ERROR state instead of staying in RESIZING state.
Backups should no longer go into COPY_ERROR state when the backup copy operation fails.
Creation date will no longer be set to None if build retries occur.
Redis backups should now work.
Known issues#
None for this release
v3.10.0, October 27, 2020#
What’s new#
Upgrading a single instance puts both the instance and its upgraded replica into a VERIFY_UPGRADE state.
Note: Both the instance and upgraded replica remain in this state until the upgraded replica is detached from the instance.
This keeps the data current in the upgraded replica while the customer validates that their application doesn’t have any issues with the upgraded replica and plans a maintenance to disconnect their application from the instance and connect to the upgraded replica.
You can set up scheduled backups to take a full backup every day instead of taking a full backup one day a week and incrementals on the other days.
On-demand upgrade of HA groups:
You can upgrade HA MySQL 5.1/5.6 to MySQL 5.7.
You can upgrade HA MariaDB 10/10.1 to MariaDB 10.4.
You can upgrade HA MariaDB 10.4 to MariaDB 10.4enc.
General availability of backup copy functionality for on-demand and scheduled backups.
Resolved issues#
Request for an on-demand upgrade of single instance is rejected if the instance is a source to or a replica of another instance.
The final state for a revived instance is ACTIVE instead of REVIVED.
Known issues#
None for this release
v3.9.0, August 12, 2020#
What’s new#
Encrypted backups for MariaDB 10.4enc instances.
MariaDB 10.1enc instances can be upgraded to a new MariaDB 10.4enc instances
Backups can be copied, on-demand, to other CDB regions
Resolved issues#
Restores using a backup created for a obsolete datastore version should no longer fail.
Upgrades of instances that have database users specified in stored procedures should no longer fail.
Adding replicas for Percona 5.6 HA groups should no longer fail.
Resizes of instances with large and loaded root partitions should have a better chance of success
Known issues#
None for this release
v3.8.0, June 2, 2020#
What’s new#
Percona version 5.7 is available for instance and HA group provisioning.
MariaDB version 10.4enc is available for instance and HA group provisioning. This version has data-at-rest encryption enabled.
Binary logging has been disabled by default for MySQL 8.0 instances.
Additional options are available for the on-demand upgrade for single instances of MySQL 5.6 and MariaDB 10.4:
You can upgrade MySQL 5.6 to MariaDB 10.4enc.
You can upgrade MariaDB 10.4 to MariaDB 10.4enc.
The API no longer allows you to specify the deprecated datastore versions, MySQL 5.1/5.6 and MariaDB 10/10.1, when building new instances or HA groups.
Note: This does not impact existing instances or HA groups with respect to adding replicas, failovers, etc.
Resolved issues#
Modifying only a user’s password now works as expected.
The InternalServerError response has been replaced with the ACLNotFound response when you make a request to delete an ACL from an HA group with no ACLs.
Known issues#
None for this release
v3.7.0, April 28, 2020#
What’s new#
On-demand upgrade for single instances of MySQL 5.1/5.6 and MariaDB 10/10.1:
You can upgrade MySQL 5.1/5.6 to MySQL 5.7.
You can upgrade MariaDB 10/10.1 to MariaDB 10.4.
EOL datastore versions, MySQL 5.1/5.6 and MariaDB 10/10.1, have been deprecated and are no longer available for selection when building new instances or HA groups.
Note: This does not impact existing instances or HA groups with respect to adding replicas, failovers, etc.
Resolved issues#
None for this release
Known issues#
None for this release
v3.6.1, March 18, 2020#
What’s new#
None for this release
Resolved issues#
Backups with new backup strategy, introduced in previous release, no longer fail immediately
Backups of databases within 10% of the database volume size are no longer rejected
Incorrect backup type is no longer reported for failed backups
Replication status alert for Percona 5.6 replicas no longer reports missing package
Full backups are no longer created for Incremental backups
Known issues#
None for this release
v3.6.0, February 4, 2020#
What’s new#
MariaDB version, 10.4, available for Instance and HA Group provisioning
Resolved issues#
None for this release
Known issues#
None for this release
v3.5.0, November 6, 2019#
What’s new#
None for this release
Resolved issues#
Monitoring for 8.0 instances is enabled
Replication status alert for replicas does not report missing package
Requested number of users is returned when listing database users for an instance
Database access is removed for original user name when user is renamed
Known issues#
None for this release
v3.4.0, September 24, 2019#
What’s new#
MySQL version, 8.0, available for Instance and HA Group provisioning
Modified the 64Gb flavor to use 16 CPUs instead of 14
Resolved issues#
Large backups no longer timeout during disk formatting operations
Known issues#
None for this release
v3.3.0, July 01, 2019#
What’s new#
Improved backup process to re-authenticate if auth token expires during backup processing
Resolved issues#
The database list for MySQL 5.7 instances no longer includes system databases
Backup with an auxiliary volume should no longer abort immediately
Volumes can be resized for v1 instances in Sydney and Hong Kong data centers
Known issues#
None for this release
v3.2.1, April 22, 2019#
What’s new#
None for this release
Resolved issues#
Regeneration of SSL certificates should result in hostnames being used for common name
Known issues#
Backup with auxiliary volume fails immediately if cleanup operations are not successful
v3.2.0, April 8, 2019#
What’s new#
None for this release
Resolved issues#
Auth tokens expiring during long running backups should no longer result in a failed backup
Restores should no longer timeout if a retry with an auxiliary volume is required
Incremental restores should no longer fail immediately when a retry with an auxiliary volume is required
Known issues#
None for this release
v3.1.0, February 27, 2019#
What’s new#
Source/Replica links are now provided in response when getting details of an HA group
Backup requests are retried with an auxiliary volume if the first attempt fails
Resolved issues#
Response when getting list of instances is no longer limited to 20 when specifying a limit larger than 20
Known issues#
None for this release
v3.0.0, January 30, 2019#
What’s new#
This release includes the following updates:
Major infrastructure upgrade to move forward with OpenStack version alignment
Resolved issues#
Changing only dynamic variables for a database configuration should no longer require a restart
Restores should no longer fail immediately if a retry with an auxiliary volume is required
Known issues#
None for this release
v2.47.0, January 28, 2016#
What’s new#
This release includes the following updates:
Change wording and behavior of public client.
Move keystone in requirements txtAdds “schedule” field to HA GET call.
Resolved issues#
None for this release
Known issues#
None for this release
v2.40.0, November 12, 2015#
What’s new#
This release include the following updates:
Documentation:
Added the new API operation Change database instance name.
Resolved issues#
None for this release
Known issues#
None for this release
v2.36.0, October 14, 2015#
What’s new#
Scheduled Backup Fixes:
When a replication setup is converted to high availability (HA), the automated backup schedule for the replication is converted as well.
HA MySQL Fixes:
Added checks for HA group actions.
Resolved issues#
None for this release
Known issues#
None for this release
Documentation Changes#
The API reference documentation includes the following updates:
Added volume and flavor info to the List HA database instance details API operation.
Added a note about converting an automated backup schedule, if a source/replica has automated backups enabled, to the Convert replication setup to HA API operation section. The schedule is converted to an HA group automated backup schedule, with the source ID set to the HA ID. The day, hour and minute settings are the same as the source or replica schedule.
Added a warning about the source instance changing to the RESTART state when it is enabled as the master during replication setup.
v2.34.0, October 1, 2015#
What’s new#
The following API operations were added:
Convert replication setup to HA
Resize volume for an HA instance
Resize flavor for an HA instance
For details, see the API reference.
Resolved issues#
None for this release
Known issues#
None for this release
v2.30.0, September 17, 2015#
What’s new#
A new feature was added to allow users to configure the number of full backups. For details see Create scheduled backups.
Resolved issues#
Updated API operations that had malformed instances.
Known issues#
None for this release
v2.31.0, September 10, 2015#
What’s new#
An API operation was added that enables you to update the backup schedule for a specified schedule by using the schedule ID. For details see Update schedule for backups by schedule ID.
Resolved issues#
None for this release
Known issues#
None for this release
Documentation changes#
The API reference documentation includes the following updates:
Added the Update schedule for backups by schedule ID operation.
Updated the Create scheduled backup operation to provide additional information about the process for creating a scheduled backup.
v2.30.0, September 2, 2015#
What’s new#
The v2.30.0 release is a maintenance release that does not include any new features or changes.
Resolved issues#
None for this release
Known issues#
None for this release
v2.28.0, August 25, 2015#
What’s new#
The following response parameters were added to the List all datastore types operation:
ha_supportedreplication_supported
Resolved issues#
None for this release
Known issues#
None for this release
v2.27.0, August 11, 2015#
What’s new#
The Add replica to HA Instance Group operation was added. This operation adds a replica node to the HA group.
Resolved issues#
None for this release
Known issues#
None for this release
v2.26.0, July 30, 2015#
What’s new#
This release does not include any new features.
Resolved issues#
Updated API operations that had malformed instances.
Known issues#
None for this release
v2.23.0, July 8, 2015#
What’s new#
Incremental backups are no longer labeled as incremental.
A 1-to-1 relationship between a schedule and an instance has been established.
When you specify that a
full day!=today, no incremental backup is performed until after the full date.
Resolved issues#
None for this release
Known issues#
None for this release
v2.22.0, June 25, 2015#
What’s new#
High Availability (HA) support has been added for Percona 5.6 and MariaDB 10.
Resolved issues#
None for this release
Known issues#
None for this release
v2.20.0, June 25, 2015#
What’s new#
A new configuration value with a shortened timeout was added for get_volume_info RPC calls.
Resolved issues#
None for this release
Known issues#
None for this release
v2.19.0, June 4, 2015#
What’s new#
A feature was added to Get instance that now shows if a schedule exists.
Resolved issues#
None for this release
Known issues#
None for this release
v2.18.0, June 4, 2015#
What’s new#
A feature was added to prevent actions on a replica for instance users and databases.
A feature was added to actually delete backup files from Cloud Files.
Resolved issues#
None for this release
Known issues#
None for this release
v2.17.0, May 19, 2015#
What’s new#
An issue was identified that MySQL sql_mode ANSI_QUOTES breaks guest agent queries.
A feature was added to enforce minimum instance size rules for replication.
A feature was added to support string quoting in instance configurations.
Resolved issues#
None for this release
Known issues#
None for this release
v2.16.0, May 11, 2015#
What’s new#
when you delete an instance, incomplete backups of the instance will now fail.
Resolved issues#
The replica_of attribute in the slave instance was fixed.
Known issues#
None for this release
v2.15.0, April 29, 2015#
What’s new#
None for this release
Resolved issues#
This release includes an update to fix an incorrect time stamp that was listed on instance creation.
Known issues#
None for this release
v2.14.0, April 10, 2015#
What’s new#
The release numbering scheme has been changed to make it easier to accomodate hotfixes by using the last number. For example, v2.14.1 could be used as the release number for a hotfix for v2.14.0.
The
include_replicasquery parameter has been added for filtering out replicas from the List all database instances and List all replicas and replica source database instances API operations. For examples, see List all instances/replica sources and filter out replicas.
Resolved issues#
Fixed the following backup issues:
The authentication token was refreshed when it expired in the middle of the backup process.
Uncompleted backups are prevented from being restored.
The correct status of the backup (failed, succeeded, and so on) was not reported.
Known issues#
None for this release
v2.13.0, April 10, 2015#
What’s new#
A new API operation List replicas for source instance was added.
Logic was added to prevent users from changing the password of the replica user and causing any inadvertent change.
Resolved issues#
Fixed backup operations to ensure successful completion of the backup process.
Known issues#
None for this release
v2.12.0, February 12, 2015#
What’s new#
The capability to list replicas for a source database instance was added to the List replicas for source instance instances operation operation.
The request body of the Detach replica operation operation can now contain only the
replica_ofattribute.
Resolved issues#
None for this release
Known issues#
None for this release
v2.11.0, January 29, 2015#
What’s new#
Note that database configuration parameters are not the same across regions.
Resolved issues#
None for this release
Known issues#
None for this release