- constrain tempest on the old legacy jobs we have in stable/ussuri to a tag that doesn't need this latest version of oslo.utils;
- replace all the test jobs in stable/ussuri to the zuulv3 native jobs.
- figure out a way to stop installing/using tempest from the global python namespace, and use a tempest virtualenv.
I expect all third party CI jobs on stable branches to be broken as well.
An ussuri job defined in a native zuulv3 format doesn't hit this issue: https:/ /review. opendev. org/c/openstack /manila- tempest- plugin/ +/725692
In this job tempest plugin is installed into a virtualenv, which always uses tempest requirements from master:
https:/ /github. com/openstack/ devstack/ blob/a64c843052 529cf5c8ac8cf8e b46c59b103b4b47 /lib/tempest# L731-L743
So options here seem to be:
- constrain tempest on the old legacy jobs we have in stable/ussuri to a tag that doesn't need this latest version of oslo.utils;
- replace all the test jobs in stable/ussuri to the zuulv3 native jobs.
- figure out a way to stop installing/using tempest from the global python namespace, and use a tempest virtualenv.
I expect all third party CI jobs on stable branches to be broken as well.