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.
DescriptionJustin Sherrill
2015-03-18 18:33:09 UTC
Description of problem:
Currently restarting pulp_workers will cause any 'stuck' or running tasks to be cancelled. This is fine and expected. The problem is that katello isn't recognizing those as an error, but instead is treating them as successful and continuing normally.
Version-Release number of selected component (if applicable):
6.1.0
How reproducible:
Always
Steps to Reproduce:
1. Start some long process like a content view publish
2. After it has gotten started, but before it finishes kill the pulp workers
3. Watch the task complete successfully, even though some of the pulp tasks were 'cancelled'
note it may take several tries to get this right
Actual results:
dynflow process 'completes' successfully even though some things did not occur
Expected results:
The task should error, and require the user to resume it
Additional info:
Comment 1RHEL Program Management
2015-03-18 18:43:22 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Moving to POST since upstream bug http://projects.theforeman.org/issues/10249 has been closed
-------------
Ivan Necas
Applied in changeset commit:katello|d5ad3e7d451968bfbe28adc3cc35e93434299411.
commit c6f37f5152170e9c88a0f6061f214e06e2a678f8
Author: Ivan Nečas <inecas>
Date: Thu Apr 23 10:48:07 2015 +0200
Fixes #10249 - treat canceled tasks as errors
This gives the indication that the task was not finished properly and
should be resumed. Without this patch, we always treated it as
success, which is not correct behavior.
(cherry picked from commit d5ad3e7d451968bfbe28adc3cc35e93434299411)
I think this seems OK? I encountered other issues trying to reproduce this one but in general when I managed to get a task to "not finish" (stopping services etc.), it did not return a success, and I was (sometimes) subsequently able to resume the sync.
Myriad other issues are being investigated; if I see this arise again, I will reopen.
Snap5 Compose 2