[all] client functional jobs are broken by new tox release
Hi, Another fun moment :-) New tox 4.46.0 was released quite recently. This release requires virtualenv 20.39.0 which was released a few days ago (See https://github.com/tox-dev/tox/issues/3069 for details). This conflict with virtualenv pinned to 20.38.0 in upper-constraints and we found some of the functional jobs of client libs (at the moment of writing, cinderclient and heatclient at least) due to the following behavior. - These jobs first install devstack and run tox to test clients accessing API - tox in current CI image is <4.46.0, but it is updated to 4.46.0 due to somehow neutron plugin installs tox (it loos like this is not actually required and I'm trying to get rid of it by https://review.opendev.org/c/openstack/devstack/+/977970 ) - however virtualenv is still pinned to 20.38.0 due to uc. The typical error caused by this combination is "AttributeError: 'PythonSpec' object has no attribute 'machine'" # See https://zuul.opendev.org/t/openstack/build/3f2448194352452a9f674d6c0648b816 There is still some discussions about whether we can bump virtualenv in u-c[2]. Please be aware of this and avoid recheck for now. [2] https://review.opendev.org/c/openstack/requirements/+/977947 -- Takashi Kajinami irc: tkajinam github: https://github.com/kajinamit launchpad: https://launchpad.net/~kajinamit
The requirements update to pull new virtualenv[1] is being merged. We also prepared the devstack update to drop installation of tox[2], which is the current trigger of this incompatible combination in CI, and it is also being merged. Once one of these is (or both of these are) merged I expect the CI will be unblocked. While we worked on these, it eventually turned out the real root cause is the outdated minversion of virtualenv tox declares. This was fixed[3] in 4.46.3 but we still have to get tox 4.46.0-2 yanked so that these are not installed when virtualenv is capped. I expect this might take some time (I'm personally unsure if yank is accepted really given the number of releases they have to yank), we anyway need [1] and [2] to unblock us as soon as possible. [1] https://review.opendev.org/c/openstack/requirements/+/977947 [2] https://review.opendev.org/c/openstack/devstack/+/977970 [3] https://github.com/tox-dev/tox/pull/3829 On 2/25/26 11:55 PM, Takashi Kajinami wrote:
Hi,
Another fun moment :-)
New tox 4.46.0 was released quite recently. This release requires virtualenv 20.39.0 which was released a few days ago (See https://github.com/tox-dev/tox/issues/3069 for details). This conflict with virtualenv pinned to 20.38.0 in upper-constraints and we found some of the functional jobs of client libs (at the moment of writing, cinderclient and heatclient at least) due to the following behavior.
- These jobs first install devstack and run tox to test clients accessing API
- tox in current CI image is <4.46.0, but it is updated to 4.46.0 due to somehow neutron plugin installs tox (it loos like this is not actually required and I'm trying to get rid of it by https://review.opendev.org/c/openstack/devstack/+/977970 )
- however virtualenv is still pinned to 20.38.0 due to uc.
The typical error caused by this combination is "AttributeError: 'PythonSpec' object has no attribute 'machine'"
# See https://zuul.opendev.org/t/openstack/build/3f2448194352452a9f674d6c0648b816
There is still some discussions about whether we can bump virtualenv in u-c[2]. Please be aware of this and avoid recheck for now.
[2] https://review.opendev.org/c/openstack/requirements/+/977947
participants (1)
-
Takashi Kajinami