2026.1 Series Release Notes¶

25.1.0-4¶

Fixed a typo in the default storage driver name (swfit instead of swift) in the task manager backup creation path. When a backup request arrived without storage_driver in its metadata, the Swift endpoint URL was not injected and the guest agent rejected the backup with “Missing swift_url in backup metadata”, leaving the backup record stuck in the NEW state.

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.

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.

Introduced a new configuration option [DEFAULT]/cinder_client_version with default value set as 3. This allows operators to supply the intended version of Cinder API to interact with.

Logic for fetching Cinder API version has been fixed, and it no longer relies on the [DEFAULT]/cinder_service_type value. This allows to have a cinder_service_type defined as block-storage, or any other name which is not versioned.

Fixes MariaDB when datastore use official MariaDB dockerhub images. MariaDB starting from version 10.7 use different default path to configuration file.

Trove now unmounts the data volume before rebuilding an instance to reduce the risk of data corruption.

Allow creating configurations for disabled datastore versions. This improves the user experience by not forcing users with instances based on outdated datastore versions to upgrade.

Implements deletion of expired running backups. Allows manual deletion of running backups after CONF.running_backups_expires days since creation.

Fixes incorrect root status reporting. root show could report “is_root_enabled”: True after root was disabled; the status now reflects the actual instance state while preserving root_enabled_history logic.