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:
Sync / publish tasks cancelled in the UI are not actually getting cancelled when the user performs a cancel. The worker proccess continues to execute the task. Pulp's REST API says the cancellation is successful and the task status is marked as CANCELLED. However, the details of the task continue to get updated as a sync or publish continues to run. Users can experience delays in other tasks starting because the workers are busy executing cancelled tasks.
Version-Release number of selected component (if applicable):
Any release of Satellite 6 that uses python2-celery 4.0.2.
How reproducible:
Every time
Steps to Reproduce:
1) Start a sync of a single repository.
2) Look at output of 'top' and make note of CPU usage of a single celery process that is performing the sync.
3) Go to the task details and click the cancel button.
4) Look at the output of 'top' and observe that the same celery process is still using just as much CPU.
Actual results:
The celery process continues executing the task.
Expected results:
Celery process stops executing the task.
Additional info:
The actual problem is in the kombu package. There is already a patch for it upstream. https://github.com/celery/kombu/pull/1029/
Comment 3pulp-infra@redhat.com
2019-03-28 08:31:35 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2019-03-28 08:31:35 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Verified in Satellite 6.5.0 Snap 23
Followed the reproducer steps.
Upon canceling the sync, you can see the celery worker being killed and replaced.
See attached video 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/RHSA-2019:1222
Comment 15pulp-infra@redhat.com
2019-05-22 19:31:47 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 16pulp-infra@redhat.com
2019-05-30 17:02:08 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.