Control: reassign -1 openstack-clients On 2025-01-22 15:30:43, Antoine Beaupré wrote: > Control: reassign -1 python3-keystoneauth1 > Control: affects -1 cumin > > I've struggled to get a backtrace from cumin because it catches all > exceptions in its main() function. But by removing that handler, I could > see a backtrace.. > > Mysteriously, the entry point in cumin is actually: > > -> from keystoneauth1 import session as keystone_session
So in https://phabricator.wikimedia.org/T384539, volans did a nice job at tracing this a little further and correctly identified that just keystoneauth1 is not enough to trigger the bug. You need a *combination* of packages... It looks like eventlet declares a socket API that's not properly compatible with what's expected, but that codepath just gets triggered when other deps get brought in. I don't know exactly which package to pin this on, but this feels like all those packages are under the openstack umbrella. And since openstack-clients reliably triggers the issue, then I think it's best to assign it there. Reproducer: $ docker run --rm -ti debian:sid # apt update # apt install python3-keystoneauth1 # apt install openstack-clients # python3 -c 'import keystoneauth1' Note that just installing openstack-clients directly does *not* trigger the bug: you need to *first* install keystoneauth1, *then* openstack-clients, it's pretty weird. a. -- Le pouvoir n'est pas à conquérir, il est à détruire - Jean-François Brient, de la servitude moderne
