| opendevreview | melanie witt proposed openstack/tempest master: Wait for volume "in-use" in test_encrypted_cinder_volumes_resize_revert https://review.opendev.org/c/openstack/tempest/+/990999 | 00:25 |
|---|---|---|
| elodilles | note that recent upper-constraints bump ( https://review.opendev.org/c/openstack/requirements/+/990790 ) broke stable/2025.1 (epoxy) ubuntu jammy based tempest jobs, as rpds-py 2026.5.1 version removed py310 support, which is jammy's default python version :/ | 14:26 |
| elodilles | what is the nice approach to fix this? | 14:27 |
| clarkb | is this usually when we switch to a tagged tempest release? | 14:49 |
| elodilles | clarkb: not yet. the 2025.1-last tag should be introduced when 2025.1 is not maintained anymore (goes to Unmaintained or EOL) | 14:52 |
| clarkb | elodilles: but tempest will tag early when master is no longer compatible with stable branches so that stable branches can use the tags | 14:55 |
| clarkb | (since tempest is not branched) | 14:55 |
| mnasiadka | elodilles: should we add rpds-py version with python version constraint? | 14:59 |
| mnasiadka | But another thing is we should have a mechanism that uses stable branch UC in stable branch tempest tests? | 15:00 |
| elodilles | clarkb mnasiadka : i'm not sure, hence i'm asking what is the practice here o:) | 15:00 |
| elodilles | mnasiadka: actually, tempest is installed in its own venv, with master constraints. this worked so far i think | 15:01 |
| elodilles | probably so far, packages haven't been dropping old python versions so aggressively :/ | 15:02 |
| mnasiadka | Might be, I think the fastest solution is to fix that in requirements - but maybe tempest should start using stable u-c on stable branches | 15:03 |
| mnasiadka | elodilles: something like https://review.opendev.org/c/openstack/requirements/+/991126 ? | 15:07 |
| mnasiadka | frickler: ^^ fyi | 15:07 |
| elodilles | mnasiadka: ah, yes, you are right, that will be it! thanks o/ | 15:08 |
| frickler | no, we got rid of py3.10 constraints intentionally | 15:09 |
| mnasiadka | Yeah, that’s true - just trying to find a quick solution which we can revert once the correct solution lands | 15:10 |
| frickler | iiuc the solution is to use tempest 46.3.0, which is pinned to stable/2026.1 reqs | 15:11 |
| mnasiadka | So override-checkout in all projects? That’s a fun task | 15:12 |
| mnasiadka | Proposed this in neutron-t-p - let’s see if that helps: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/991129 | 15:15 |
| timburke | i was expecting to be able to set TEMPEST_VENV_UPPER_CONSTRAINTS (as in https://review.opendev.org/c/openstack/swift/+/990959), but that didn't actually seem to do much (the job still wound up using master constraints) | 15:15 |
| gmaan | there are some more place we need to pin it but pinning based on job is possible with TEMPEST_VENV_UPPER_CONSTRAINTS but that needs to be done in plugin side also like neutron-tempest-plugin did | 15:16 |
| gmaan | elodilles: mnasiadka frickler if requirement change to have py3.10 constraints is not acceptable then I need to drop the py3.10 support from tempest and release a new tag | 15:18 |
| gmaan | and use that tag for the 2025.1 jammy testing. that is proper solution for that and we did in past | 15:19 |
| gmaan | let me start the work for that today | 15:19 |
| elodilles | gmaan: ah, good to know. i did not remember that | 15:19 |
| gmaan | before releasing the tempest, we need to do some pre-work on tempest side on tox.ini constraints. I will propose those after my morning meetings | 15:23 |
| mnasiadka | Thanks gmaan | 15:24 |
| opendevreview | Maor Blaustein proposed openstack/devstack master: Devstack OVN support for resource_provider_* configuration https://review.opendev.org/c/openstack/devstack/+/991136 | 15:25 |
| gmaan | we usually keep old python version support in tempest as long as they are working. once they are broken (mostly due to constraints ) then we start that version support drop process, like this case. | 15:25 |
| timburke | again, i don't think TEMPEST_VENV_UPPER_CONSTRAINTS actually works for this -- it causes UPPER_CONSTRAINTS_FILE and TOX_CONSTRAINTS_FILE to get exported during run-devstack, but we seem to have a fresh environment when we later get to run-tempest, so it still uses constraints from master | 15:28 |
| gmaan | yeah, that is coming from the tempest role run-tempest, we pin the constraints threre but that is per branchs not per job/distro | 15:31 |
| sean-k-mooney | the requireemt repo can technnly expre per python verion requireemnt so you coudl pin rpds-py to the prvious version fo py 3.10 | 17:49 |
| sean-k-mooney | but your aslo corerct that on master we should not need to do that | 17:49 |
| frickler | the reqs repo no longer runs py3.10 checks, so we would really like to avoid that. we could revert the rpds-py bump for a week if that would be really needed | 17:52 |
| sean-k-mooney | ya im not a fan of that solution eithe rfor what its worth | 17:53 |
| sean-k-mooney | the per stable branch version fo the tempet job on master could just point to an older requirements file | 17:53 |
| sean-k-mooney | anyways im sure gmaan's got this | 17:54 |
| sean-k-mooney | it sound like its not the first time this has happended | 17:55 |
| gmaan | yeah, this is usually happen when we move the min supported python version | 17:55 |
| opendevreview | Ghanshyam Maan proposed openstack/tempest master: Drop py3.10 from Tempest https://review.opendev.org/c/openstack/tempest/+/991161 | 17:57 |
| sean-k-mooney | gmaan: so regarding 2025.1 jammy was only included in https://github.com/openstack/governance/blob/master/reference/runtimes/2025.1.rst as part fo the addtional testing for smoth upgrade so i woudl expect this mainly to have impacted the greade jobs correct | 18:01 |
| sean-k-mooney | there may have been some other jobs that had not moved to noble in some cases too | 18:01 |
| gmaan | yes, that is the only stable jobs failing. rest all on 2025.1 run on noble and green | 18:02 |
| opendevreview | Ghanshyam Maan proposed openstack/tempest master: Set upper-constraints if TEMPEST_VENV_UPPER_CONSTRAINTS is set https://review.opendev.org/c/openstack/tempest/+/991180 | 19:10 |
| opendevreview | Ghanshyam Maan proposed openstack/whitebox-tempest-plugin master: Drop python 3.10 https://review.opendev.org/c/openstack/whitebox-tempest-plugin/+/991183 | 19:19 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!