Control: reassign -1 openstack-clients
On 2025-01-24 12:44:22, Thomas Goirand wrote:
> On 1/24/25 10:52, Riccardo Coccioli wrote:
>> 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 <https://
>> phabricator.wikimedia.org/T384539#10488086>
>
> Hi,
>
> I just tried, and couldn't reproduce.
>
> Do you have recommends enabled? (I don't)
I think the problem here is my reproducer was incorrect. Above, Riccardo
has a correct reproducer, but mine said:
$ docker run --rm -ti debian:sid
# apt update
# apt install python3-keystoneauth1
# apt install openstack-clients
# python3 -c 'import keystoneauth1'
I don't know how I came up reproducing with that, but now I can't at
all. What I need is *exactly* like Riccardo says (although the upgrade
is not necessary). In a fresh sid container (but I suspect a VM would do
the same):
apt update
apt install python3-keystoneauth1
apt install python3-eventlet python3-trio
apt install openstack-clients
python3 -c 'from keystoneauth1 import session'
The critical difference with my reproducer is that we install eventlet
and trio *and* it actually does the `import session` to specifically
import that session module or object or whatever this is.
I couldn't reproduce with my reproducer, but now i can with this.
Note that if you run the above in a Dockerfile/Containerfile, you might
have false negatives (i.e. won't be able to reproduce) because Docker
will cache container layers.
A clean Containerfile to reproduce the issue would look like this:
FROM debian:sid
RUN apt update
RUN apt install -y python3-keystoneauth1; apt install -y python3-eventlet
python3-trio; apt install -y openstack-clients
RUN python3 -c 'from keystoneauth1 import session'
Then run `podman build --no-cache .` in the directory where the
containerfile is stored.
It's important to start from a clean environment (a VM freshly installed
or a new container), because the package install is not idempotent:
something fishy is happening with the package install order and if you
mess it up, you can't reproduce.
With the above containerfile, or the above procedure, I can reliably
reproduce this bug with only openstack-related packages.
I'm therefore reassigning this back to openstack-clients. I would
appreciate if the bug isn't reassigned back to cumin, as this is clearly
not a cumin problem. If it is reassigned back there, I will simply close
the issue as wontfix.
Thanks!
a.
--
Les plus beaux chants sont les chants de revendications
Le vers doit faire l'amour dans la tête des populations.
À l'école de la poésie, on n'apprend pas: on se bat!
- Léo Ferré, "Préface"
