Current Series Release Notes¶

26.0.0.0rc1-34¶

Adds management API endpoints to load and remove datastore version configuration parameters.

Adds management API endpoints to list, add, and delete flavor associations for datastore versions.

Adds management API endpoints to list, add, and delete volume type associations for datastore versions.

Fixes backup deletion failures caused by comparing an offset-aware current time with an offset-naive backup creation timestamp. LP#2166063

Fixed database status detection for stopped containers that retain a healthy Docker health status. Trove now identifies an exited container as SHUTDOWN before evaluating its health status.

Fixed database validation against the ignore_dbs option to use the configuration for the instance’s datastore manager. This prevents a reserved-database list for one datastore from being applied to another.

Fixed user validation against the ignore_users option to use the configuration for the instance’s datastore manager. This prevents a reserved-user list for one datastore from being applied to another.

Fixes an instance becoming unable to retry a datastore restart after the guest agent times out. The instance action validator now uses the same effective guest-agent status as the instance detail API and reports the datastore service status that blocked an action.

MySQL replication instances now use the ROW binary logging format instead of MIXED. Previously, enabling replication changed binlog_format to MIXED on the replication source and replicas, which would override the default ROW value on existing instances. Existing replication setups are not modified. Rebuilding existing MySQL instance will change MIXED value to ROW.

Reduced PostgreSQL connection latency in some environments by removing the localhost pg_hba rule, avoiding reverse DNS lookups.

Fixed instance access updates to preserve the current is_public and allowed_cidrs values when the corresponding fields are omitted from the request.

Removes character_set_client, character_set_connection, character_set_database, character_set_results, collation_connection, and collation_database from the shipped MariaDB configuration parameter validation rules. These variables are not valid MariaDB server option-file settings and can prevent an instance from starting when used in a configuration group.

Rules already loaded for existing datastore versions are not changed automatically. Cloud administrators should remove these parameters from each affected MariaDB datastore version with the management API, or delete and reload that version’s complete validation rule set.

Assigns a unique service status code to the RESTARTING state. Previously, RESTARTING and UPGRADING shared the 0x22 code, which made them indistinguishable in code-based status comparisons and lookups.

Updates the datastore version in guest_info.conf after a successful database upgrade. This keeps the guest agent configuration in sync with the running datastore version.

Database shutdown requests now use agent_call_high_timeout instead of agent_call_low_timeout. This provides more time for a database under load to stop before the guest agent call times out.

Validate that the configuration datastore version matches the datastore version of the instance when creating an instance with a configuration. This prevents instances from being created with a configuration intended for a different datastore version.