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.
Steps to test:
Steps to Reproduce:
1. Invoke some bigger CV publish/promote (with more repos inside)
2. While there are pulp celery workers processing the sync/publish tasks, kill some of them via "kill -SIGHUP <pid>"
3. Check /var/log/messages
4. Verify in the web UI that the foreman task errors out
5. Verify that the task can be resumed and completes successfully
Expected result:
3. log should not show error message or traceback
4. Foreman task should show task error out
5. Task should complete successfull
Actual Result:
3. Log still shows traceback
4. Action:
Actions::Pulp::Repository::CopyAllUnits
{"pulp_tasks"=>
.......................
"queue"=>
"reserved_resource_worker-5@<hostname>",
"state"=>"error",
"worker_name"=>
"reserved_resource_worker-5@<hostname>",
"result"=>nil,
"error"=>
{"code"=>"PLP0049",
"data"=>{"task_id"=>"c2fffb9a-67c4-4238-8fb2-61bf692c40b9"},
"description"=>
"Worker terminated abnormally while processing task c2fffb9a-67c4-4238-8fb2-61bf692c40b9. Check the logs for details",
"sub_errors"=>[]},
"_id"=>{"$oid"=>"6033cbf0dbf4aca8772c8791"},
"id"=>"6033cbf0dbf4aca8772c8791"},
.........................................
5. Task completes successfully
Name:Publish content view 'some'; organization 'Default Organization'
Start at:1 hour ago
Result: success
Started at:1 hour ago
Triggered by:admin
Ended at:56 minutes ago
Execution type:Immediate
Start before:-
Though there is still a traceback in the log, this does not affect how the fix to the problem was applied. The task error out and does not hang anymore and users can resume the task without issues.
Verified on 6.8.4_02 with pulp-rpm-plugins-2.21.3.3-1.el7sat.noarch
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 (Satellite 6.8.4 Async Bug Fix Update), 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-2021:0654
Comment 23pulp-infra@redhat.com
2021-05-17 10:12:14 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 24pulp-infra@redhat.com
2021-05-17 10:12:18 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.