I proposed https://review.opendev.org/c/openstack/requirements/+/977591 to bump the packaging library version. If you know the exact job failing, we can use depends-on to check whether this can resolve the failure. On 2/23/26 2:08 PM, Takashi Kajinami wrote:

I think the immediate fix is to bump packaging in upper-constraints. From the log I see packaging 26.0.0 was first installed by ensure-tox role but it is downgrade when the other softwares are installed with u-c.

For stable branches we likely need to cap tox (but that requires us to add ensure_tox_version in many places like we did for tox<4 pi), or we could discuss whether we can bump the upper constraint of packaging.

On 2/23/26 8:18 AM, Brian Haley wrote:

...

An update...

On 2/22/26 2:53 PM, Brian Haley wrote:

...

Hi,

Started seeing this failure yesterday in the neutron-functional job:

   ModuleNotFoundError: No module named 'packaging.pylock'

Jens Harbott noticed there was a new tox release just the other day, version 4.44.0 which included a pylock change [0].

When I updated my neutron change to pin tox<4.44.0 all was well, so I opened an issue with tox [1].

Not sure what the short-term solution should be here if that cannot be fixed quickly, can we set an upper-limit globally, at least until we get 2026.1 out?

Thanks,

-Brian

[0] https://github.com/tox-dev/tox/commit/7b601a77e8376b9198b7203b4e644873cc543e... [1] https://github.com/tox-dev/tox/issues/3811

...

Full ouptput at https://paste.opendev.org/show/bawqTgzkecxaK5DVEEAA/

I figured it was another issue with a new release of the packaging library as I see a 26.0 now, but upper-constraints is pinned to ==25.0 so I don't see how it's being pulled-in. The logs do show 26.0 being used at the end so I'm confused.

I even tried to do a quick pin but it's still using 26.0:

https://review.opendev.org/c/openstack/neutron/+/977556

Have any other projects seen this? Is 26.0 causing this or is it another interaction between libraries?

Thanks for any help,

-Brian