Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I got a report that a Satellite user had it's Pulp resource_manager stuck. Here are some details:
They were no longer able to get one of their capsules to sync, and Pulp tasks would become ready for work but never get executed. This hotfix (https://bugzilla.redhat.com/show_bug.cgi?id=1491032) was applied but it did not help. It was observed that the resource_manager queue had 19K items in it.
I believe the resource_manager was deadlocked. Note there were not logs that qpid.messaging was in an illegal state. Those patches were added for deadlock detection as part of (https://bugzilla.redhat.com/show_bug.cgi?id=1279502). This means it's deadlocking for another reason.
I believe this can happen to any worker or the resource_manager on start or upon fork during operation.
I do not know how to reproduce this issue. It would occur rarely.
The Celery devs and I have discussed that there is a threading/forking incompatibility of Celery and qpid.messaging and also with Celery and the pymongo driver both of which use threading. Mixing threading and forking is a known-bad practice and can cause "deadlocking on start". This would produce effectively the same symptoms as (https://bugzilla.redhat.com/show_bug.cgi?id=1279502).
These types of issues are also reported in other various trackers:
# Celery issues
https://github.com/celery/celery/issues/4185https://github.com/celery/celery/issues/4316https://github.com/celery/celery/issues/3898https://github.com/celery/celery/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+hang
# Pymongo issues
https://projects.engineering.redhat.com/browse/DELIVERY-3041https://pulp.plan.io/issues/2979 <----- you could still deadlock on start with this. This fix only causes Pulp to fixup it's connection so that it can still run in more cases. Also not using MAX_TASKS_PER_CHILD causes it to start fewer times which doesn't fix the issue it just makes you experience it less frequently.