---- On Fri, 25 Oct 2024 14:43:03 -0700 Ghanshyam Mann wrote ---

Hello Everyone,

As you know, services and Oslo libs are dropping Python 3.8 in this cycle. Tempest is branchless, and we use Tempest master to test all supported stable branches (currently 2023.1 to 2024.2). Because Python 3.8 is still supported in stable/2023.1 to stable/2024.1 Initially, we thought of continuing the py 3.8 support in Tempest, but without Oslo libs, Tempest cannot support it. One way is to keep the python 3.8 constraints separately (either a separate file in Tempest or separate constraints for python3.8 in requirements), which stops Tempest from adding any new features from oslo/deps.

Another way (this is what we did in the previous Python version bump) is to drop the Python 3.8 support, and if anyone wants to test the cloud with Python 3.8, they can install and run Tempest on Python >=3.9 virtual env. In upstream testing, we also install and run Tempest from the virtual environment. or use the Tempest 41.0.0 (the last release which supports py3.8) to test python 3.8 cloud. This is what we did during py3.6/3.7 support removal.

- https://review.opendev.org/c/openstack/tempest/+/933398

This fix is merged, and jobs failing due to the Python 3.8 drop should pass now (from stable/2023.1 to master). For unmaintained branches, you can pin the Tempest with the compatible Tempest tag - https://docs.openstack.org/tempest/latest/tempest_and_plugins_compatible_ver... -gmann

-gmann