Different issue perhaps? Are you seeing anything in the logs that looks like this? https://github.com/rq/rq/issues/1044
On Fri, Jan 17, 2020 at 9:06 AM Daniel Alley <dal...@redhat.com> wrote: > Strange, I'm pretty sure an issue like this is why we pinned originally, > but upstream said that that particular issue was (supposedly) fixed. > > https://github.com/andymccurdy/redis-py/issues/1136#issuecomment-571168161 > > On Fri, Jan 17, 2020 at 4:15 AM Matthias Dellweg <dell...@atix.de> wrote: > >> 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 >> experience? >> >> 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, >> Matthias >> _______________________________________________ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev
