Open Stack

Hello Everyone, 

This is regarding bug: https://bugs.launchpad.net/tempest/+bug/1860033. Using Radosław's fancy statement
of 'EOLing python2 drama' in subject :).

neutron tempest plugin job on stable/rocky started failing as neutron-lib dropped the py2. neutron-lib 2.0.0
is py3 only and so does u-c on the master has been updated to 2.0.0. 

All tempest and its plugin uses the master u-c for stable branch testing which is the valid way because of master Tempest & plugin 
is being used to test the stable branches which need u-c from master itself. These failed jobs also used master u-c[1] which is trying 
to install the latest neutron-lib and failing.

This is not just neutron tempest plugin issue but for all Tempest plugins jobs. Any lib used by Tempest or plugins can drop the
py2 now and leads to this failure. Its just neutron-lib raised the flag first before I plan to hack on Tempest & plugins jobs for py2 drop
from master and kepe testing py2 on stable bracnhes.

We have two way to fix this:

1. Separate out the testing of python2 jobs with python2 supported version of Tempest plugins and with respective u-c.
For example, test all python2 job with tempest plugin train version (or any latest version if any which support py2) and
use u-c from stable/train. This will cap the Tempest & plugins with respective u-c for stable branches testing.

2. Second option is to install the tempest and plugins in py3 env on py2 jobs also. This should be an easy and preferred way.
I am trying this first[2] and testing[3].

[1] https://zuul.opendev.org/t/openstack/build/fb8a928ed3614e09a9a3cf4637f2f6c2/log/job-output.txt#33040
[2] https://review.opendev.org/#/c/703011/
[3] https://review.opendev.org/#/c/703012/


-gmanne