Hi, But this bug is also not related to Cumin in any way. Cumin doesn't have a dependency on python-eventlet nor python3-trio, which are clearly the culprit in the traceback.
I was able to reproduce the bug both on sid and trixie, you can see the details in [0] (Cumin's bug tracking system). Reporting the gist of the steps here too: apt update apt dist-upgrade apt install python3-keystoneauth1 apt install python3-eventlet python3-trio apt install openstack-clients python3 -c 'from keystoneauth1 import session' [0] https://phabricator.wikimedia.org/T384539#10488086 On Fri, Jan 24, 2025 at 10:21 AM Thomas Goirand <z...@debian.org> wrote: > Hi, > > I just tried what was said in this bug: > > apt install python3-keystoneauth1 > python3 -c "from keystoneauth1 import session as keystone_session" > > works. Then I tried: > > apt install openstack-clients > python3 -c "from keystoneauth1 import session as keystone_session" > > This worked for me as well, in a freshly installed Trixie VM. > > So therefore, I've re-assigned the bug to Cumin. If you still think > there's an issue with python3-keystoneauth1, please provide the way to > reproduce it, because I couldn't. > > What I could see in the traceback though, is that python3-trio is trying > to wrap the _stdlib_socket.socket.sendmsg api, using async. This feels > like not possible with something working with OpenStack, that typically, > would be using Eventlet, that is not async compatible, and that is > already monkey-patching the socket API. If I was the cumin maintainer, > I'd be looking into that direction instead. > > Cheers, > > Thomas Goirand (zigo) >
