[Pulp-dev] Hanging tasks (reloaded)

Matthias Dellweg dellweg at atix.de
Fri Jan 17 09:14:13 UTC 2020

Hello all,
I believe i have  found a new incarnation of hanging tasks (tm). This
time it is pulp3 and as hard to nail down as ever.
I think, it is introduced by e36e7b5f0eccc176a6e6298df29293b014f4710c.
Where the dependency on redis was dropped with the result that 3.3.smth
instead of 3.1.smth was installed.

Before filing an issue, is there anyone out there to share that

Also as a thought protocol of how to reproduce:
I have seen tasks hanging in both "waiting" and "running" state when
using the command `prestart; django-admin test pulp_deb` or `<...> test
pulpcore`. All the tasks I have seen were `sync`, `general_create` or
`general_delete` and looked like they never started to do anything for
real. To have consistent results, i had the impression that i needed to
rebuild the vagrant boxes for every bisecting step.
Also updating the python-redis package on a box that worked, produced a
hanging task in the next run.

Have a good day,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20200117/447239cd/attachment.sig>

More information about the Pulp-dev mailing list