2025.1 Series Release Notes¶
23.0.0-26¶
New Features¶
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.
Introduced a new configuration option
[DEFAULT]/cinder_client_versionwith default value set as 3. This allows operators to supply the intended version of Cinder API to interact with.
Bug Fixes¶
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.
Logic for fetching Cinder API version has been fixed, and it no longer relies on the
[DEFAULT]/cinder_service_typevalue. This allows to have a cinder_service_type defined asblock-storage, or any other name which is not versioned.
Fix PostgreSQL guest agent issues for password changes and access control.
Fix AttributeError when changing user passwords due to improper deserialization in PgSqlAdmin.change_passwords method.
Update grant_access and revoke_access methods to handle PostgreSQL changes:
Explicitly grant/revoke schema (public) access for PostgreSQL 14+
Revoke CONNECT privilege from PUBLIC to ensure proper revocation
Ensure connection is made to specific database for grant/revoke operations in PostgreSQL 16+
Fixes potential PostgreSQL shared memory exhaustion in mid-size deployments.
23.0.0¶
New Features¶
Add support of new backup storage driver “cinder”. We can provision a new replica instance or backup fast if we use cinder as the backend storage.
Upgrade Notes¶
Python 3.8 support was dropped. The minimum version of Python now supported is Python 3.9.
Bug Fixes¶
fix a bug where the trove-manage script fails to upgrade the database when the DBDatastoreVersion table is not empty.
Fix a bug where replications failed to detach from the source instance because of the upgrade of the sqlachemy library.
Fixes support for PostgreSQL v13 and above. Sets the wal_keep_size or wal_keep_segments in the instance configuration file depending on the version in the data store version name. The version number is parsed from the Datastore Version name and is exposed to the database instance configuration templates to allow the the use of conditional based on the version.