Hide Forgot
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
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Created https://bugzilla.redhat.com/show_bug.cgi?id=1552118 for 6.3
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.
Created attachment 1439365 [details] verification screenshot
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