v46.3.0 Release Notes¶
46.3.0 Release Notes¶
46.3.0¶
Prelude¶
This is an intermediate release during the 2026.2 development cycle to mark the end of support for 2024.2 release in Tempest. After this release, Tempest will support below OpenStack Releases: * 2026.1 * 2025.2 * 2025.1 Current development of Tempest is for OpenStack 2026.2 development cycle.
The pre-provisioned credentials supports the new SRBAC personas.
New Features¶
A new config option
replicationin thevolume-feature-enabledsection is added. This boolean option (default: False) allows toggling of Cinder volume replication-related test execution. When enabled, it indicates that the deployment supports volume replication features and replication tests should be executed.
Added support for the Cinder
failover_hostadmin action in the volume v3 services client. This API allows triggering a failover operation on a Cinder backend host, which is essential for testing volume replication and disaster recovery scenarios.
Added a new waiter function
wait_for_volume_replication_status()in thetempest.common.waitersmodule. This waiter polls a volume until it reaches the expected replication_status value, with configurable timeout and interval. This is useful for validating replication state transitions such as ‘enabled’, ‘copying’, ‘active’, and ‘failed-over’.
Tempest can send the
X-Service-Tokenheader in the API request to services. A test case can generate and set the service token on service clients which will be send in APIX-Service-Tokenheader.
Add support for SRBAC personas as well as system scope in the
tempest account-generatorcommand as well as in pre provisioned credentials. The below SRBAC personas are supported:system adminsystem membersystem readerproject managerproject memberproject reader
Bug Fixes¶
Fixed a bug#2143564 in the pre-provisioned credentials provider where
project_memberandproject_readerwere not guaranteed to be allocated from the same project. ThePreProvisionedCredentialProvidernow stores accounts by project name and gets the accounts based on the project name if they are requested from the same test class.