Project

Profile

Help

Issue #4581

Task Cancellation doesn't interrupt/cancel a running task with Celery 4+

Added by bmbouter 8 months ago. Updated 6 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
Due date:
Severity:
2. Medium
Version:
Platform Release:
2.19.1
Blocks Release:
OS:
Backwards Incompatible:
No
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
QA Contact:
Complexity:
Smash Test:
Verified:
Yes
Verification Required:
No
Sprint:
Sprint 51

Description

See the upstream PR fix for it here from @rohanpm https://github.com/celery/kombu/pull/1029

The fix would be to include ^ PR in the kombu packages Pulp ships.


Related issues

Copied to Pulp - Test #4728: Task Cancellation doesn't interrupt/cancel a running task with Celery 4+ NEW Actions

Associated revisions

Revision 16fd6cc9 View on GitHub
Added by dkliban@redhat.com 8 months ago

Update kombu qpid transport to correctly declare support for async event loop

fixes: #4581
https://pulp.plan.io/issues/4581

History

#1 Updated by dkliban@redhat.com 8 months ago

I've confirmed that in Pulp 2.18.1 tasks are getting marked as cancelled in the database, but the celery process continues to execute the task.

#3 Updated by CodeHeeler 8 months ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 51

#4 Updated by dkliban@redhat.com 8 months ago

  • Status changed from NEW to MODIFIED
  • Assignee set to dkliban@redhat.com

#5 Updated by bmbouter 7 months ago

  • Tags Pulp 2 added

#6 Updated by bherring 7 months ago

  • Copied to Test #4728: Task Cancellation doesn't interrupt/cancel a running task with Celery 4+ added

#7 Updated by dkliban@redhat.com 7 months ago

  • Platform Release set to 2.19.1

#8 Updated by dkliban@redhat.com 7 months ago

  • Sprint/Milestone set to 2.19.1

#9 Updated by rochacbruno 6 months ago

  • Verified changed from No to Yes

#10 Updated by dkliban@redhat.com 6 months ago

  • Status changed from MODIFIED to ON_QA

#11 Updated by dkliban@redhat.com 6 months ago

  • Status changed from ON_QA to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF