[qa][stable][tempest-plugins]: Tempest & plugins py2 jobs failure for stable branches (1860033: the EOLing python2 drama)

Radosław Piliszek radoslaw.piliszek at gmail.com
Fri Jan 17 07:49:32 UTC 2020


+1 for py3 in tempest venv. Makes most sense.

Though the test is failing now:
2020-01-17 04:30:06.975801 | controller | ERROR: Could not find a
version that satisfies the requirement neutron-lib===2.0.0 (from -c
u-c-m.txt (line 79)) (from versions: 0.0.1, 0.0.2, 0.0.3, 0.1.0,
0.2.0, 0.3.0, 0.4.0, 1.0.0, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0, 1.6.0,
1.7.0, 1.8.0, 1.9.0, 1.9.1, 1.9.2, 1.10.0, 1.11.0, 1.12.0, 1.13.0,
1.14.0, 1.15.0, 1.16.0, 1.17.0, 1.18.0, 1.19.0, 1.20.0, 1.21.0,
1.22.0, 1.23.0, 1.24.0, 1.25.0, 1.26.0, 1.27.0, 1.28.0, 1.29.0,
1.29.1, 1.30.0, 1.31.0) 2020-01-17 04:30:06.993738 | controller |
ERROR: No matching distribution found for neutron-lib===2.0.0 (from -c
u-c-m.txt (line 79))

and the reason is:
pypi: data-requires-python=">=3.6"

3.5 < 3.6

Need some newer python in there.

-yoctozepto

pt., 17 sty 2020 o 05:15 Jeremy Stanley <fungi at yuggoth.org> napisał(a):
>
> On 2020-01-16 22:02:05 -0600 (-0600), Ghanshyam Mann wrote:
> [...]
> > Second option is to install the tempest and plugins in py3 env on
> > py2 jobs also. This should be an easy and preferred way.
> [...]
>
> This makes more sense anyway. Tempest and its plug-ins are already
> segregated from the system with a virtualenv due to conflicts with
> stable branch requirements, so hopefully switching that virtualenv
> to Python 3.x for all jobs is trivial (but I won't be surprised to
> learn there are subtle challenges hidden just beneath the surface).
> --
> Jeremy Stanley



More information about the openstack-discuss mailing list