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.
Bug 1203402 - externally cancelled pulp tasks are treated as successful
Summary: externally cancelled pulp tasks are treated as successful
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: Corey Welton
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-18 18:33 UTC by Justin Sherrill
Modified: 2017-02-23 20:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-12 13:56:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10249 0 None None None 2016-04-22 15:01:28 UTC

Description Justin 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 1 RHEL 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.
Comment 3 Ivan Necas 2015-04-23 08:42:14 UTC 
Created redmine issue http://projects.theforeman.org/issues/10249 from this bug
Comment 4 Bryan Kearney 2015-04-29 14:05:24 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/10249 has been closed
-------------
Ivan Necas
Applied in changeset commit:katello|d5ad3e7d451968bfbe28adc3cc35e93434299411.
Comment 5 Bryan Kearney 2015-05-04 13:08:39 UTC 
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)
Comment 7 Corey Welton 2015-05-26 21:31:24 UTC 
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
Comment 8 Bryan Kearney 2015-08-11 13:29:51 UTC 
This bug is slated to be released with Satellite 6.1.
Comment 9 Bryan Kearney 2015-08-12 13:56:05 UTC 
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.
Note You need to log in before you can comment on or make changes to this bug.