---- On Tue, 04 Nov 2025 15:55:35 -0800 Ghanshyam Maan <gmaan@ghanshyammann.com> wrote ---
---- On Tue, 04 Nov 2025 11:25:07 -0800 Ghanshyam Maan <gmaan@ghanshyammann.com> wrote ---
Hi All,
Requirement repo has dropped the Python 3.9 constraints[1], and due to that, the Tempest gate is blocked because the Python 3.9 unit test job is failing.
We discussed this type of issue in the past[2], that if the requirement repo drops older Python version constraints, then Tempest can drop the support of that Pythion version. Tempest master can still be used to test the Python 3.9 env; for that, you need to install tempest in a Python 3.10 (or higher) env.
I have proposed the change to drop py3.9[3], and Yatin's change will unblock the stable branch testing[4]. Hold your recheck until those fixes are merged.
Both fixes have been merged, feel free to recheck.
One of the fixes[4] to pin stable constraints on stable/2024.2 and stable/2025.1 broke the stable jobs for tempest plugins. I did not think of that while merging that change. We should be using Tempest master with master constraints to test all the supported stable branches. I have created a revert of that which should unblock those stable jobs. Please hold the recheck until it is merged - https://review.opendev.org/c/openstack/tempest/+/966308 -gmaan
-gmaan
[1] https://review.opendev.org/c/openstack/requirements/+/957587 [2] https://lists.openstack.org/pipermail/openstack-discuss/2022-May/028711.html [3] https://review.opendev.org/c/openstack/tempest/+/966101 [4] https://review.opendev.org/c/openstack/tempest/+/965903
-gmaan