All tempest plugin uses the master u-c for stable branch testing which is the valid way because 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.
Tempest plugin python2 jobs on a stable branch can not install the new neutron-lib which is maintained for python3 only with metadata 'python-requires = >=3.6'.
To solve this we need to 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 which support py2) and use u-c from stable/train.
second option is to install the tempest and plugins in py3 env on oy2 jobs also. This should be easy and prefered way. let me try.
All tempest plugin uses the master u-c for stable branch testing which is the valid way because 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.
Tempest plugin python2 jobs on a stable branch can not install the new neutron-lib which is maintained for python3 only with metadata 'python-requires = >=3.6'.
[1] https:/ /zuul.opendev. org/t/openstack /build/ fb8a928ed3614e0 9a9a3cf4637f2f6 c2/log/ job-output. txt#33040
To solve this we need to 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 which support py2) and use u-c from stable/train.
second option is to install the tempest and plugins in py3 env on oy2 jobs also. This should be easy and prefered way. let me try.