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.
Description of problem:
(cloned from https://pulp.plan.io/issues/2835)
Summary
=======
Restarting a worker that is currently executing a task will leave that workers in a broken state. This issue can reproduced on both Celery 3.1.x and Celery 4.x, but only while using Qpid as a broker. I was not able to reproduce this issue while using RabbitMQ as a broker, using either version of Celery. I was also not able to reproduce this issue on versions of Pulp prior to 2.13. The means of shutting down the workers also does not appear to matter, e.g. "systemctl restart" and "pkill -9 celery; prestart" both work the same.
Repro
=====
1. Start pulp
2. Begin a task (e.g. sync)
3. While the task is running, restart the pulp worker running the task
4. After the worker has restarted, begin another task
5. Observe that the tasks are perpetually stuck in waiting
Version-Release number of selected component (if applicable): 6.3 beta, pulp-server-2.13.4.4
How reproducible: every time
Comment 2pulp-infra@redhat.com
2017-12-15 13:32:46 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 3pulp-infra@redhat.com
2017-12-15 13:32:48 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2017-12-18 15:03:12 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 8pulp-infra@redhat.com
2018-01-22 18:13:59 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 9pulp-infra@redhat.com
2018-01-29 17:02:31 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 10pulp-infra@redhat.com
2018-01-29 17:32:09 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 12pulp-infra@redhat.com
2018-02-20 18:32:55 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 13pulp-infra@redhat.com
2018-02-28 02:32:33 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 14sthirugn@redhat.com
2018-03-06 14:25:22 UTC
Verified in Satellite 6.2.15 Snap 3.
Started a repo sync.
Waited until it was syncing packages.
performed a service pulp_workers stop
Observed that the remaining steps were skipped and the task was stopped with a warning that the task was cancelled. See attached screenshot for verification.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:1672