v24.0.0 Release Notes

24.0.0 Release Notes



Remove the support of python3.5. Tempest, its plugins dependencies in ussuri cycle are python-requires>=py3.6 which makes distro not having python 3.6 to do hack to install py3.6 etc. It time to drop the py3.5 from Tempest. Last supported version of Tempest for py3.5 is 23.0.0.

This release is to tag the Tempest for OpenStack Ussuri release. This release marks the start of Ussuri release support in Tempest. After this release, Tempest will support below OpenStack Releases: * Ussuri * Train * Stein Current development of Tempest is for OpenStack Victoria development cycle. Every Tempest commit is also tested against master during the Victoria cycle. However, this does not necessarily mean that using Tempest as of this tag will work against a Ussuri (or future release) cloud. To be on safe side, use this tag to test the OpenStack Ussuri release.

New Features

  • A new config option ‘subnet_id’ is added to section ‘network’ to specify subnet which should be used for allocation of IPs for VMs created during testing. It should be used when the tested network contains more than one subnet otherwise test of external connectivity will fail. (Fixes bug

  • Add the option –worker-file in tempest run command. This is to give tempest more granularity to manually configure how the different sets of tests can be grouped to run with the different worker. You can configure tests regex to run under workers. You can also mix manual scheduling with standard one by mentioning concurrency. For example, the user can setup tempest to run with different concurrences, to be used with different regexps.

  • A new attachments client library has been introduced for the volume service.

    Initially only the show_attachment API is provided. This API requires a minimum volume API microversion of 3.27.

Upgrade Notes

  • Default value of config option CONF.placement.region is updated from RegionOne to empty string.

    As per tempest design, if tempest conf is not having any region for a service then identity region should be used. In case of placement the default value is “RegionOne” which is considered as placement region if region missing in tempest conf. In order to have identity region to be used as default we need to change to empty string for placement service. Empty string can be seen being used in other services like volume, image etc.

  • Python 2.7 support has been dropped. Last release of Tempest to support python 2.7 is Temepst 23.0.0. The minimum version of Python now supported by Tempest is Python 3.6.

  • Remove the deprecated argument os-tenant-name or OS_TENANT_NAME in favour of os-project-name argument.

  • Remove the deprecated CLI verify-tempest-config in favour of tempest verify-config command. You can use tempest verify-config CLI to verify the tempest conf file.

Deprecation Notes

  • The [compute-feature-enabled]/block_migrate_cinder_iscsi is deprecated ahead of removal in a future release. Once removed the [compute-feature-enabled]/block_migration_for_live_migration configurable will then be used to determine when to run block migration based tests during live migration.

  • The config options CONF.compute.spice_console and CONF.compute.rdp_console are deprecated because test cases using them are removed. We can add them back when adding the test cases again.

Bug Fixes

  • Fixed bug #1858417. Adding consistency group exceptions ConsistencyGroupException and ConsistencyGroupSnapshotException that didn’t exist before and caused failure in cinder-tempest-plugin.