Bug 1332609

Summary: What happens when a Pulp task is cancelled?
Product: Red Hat Satellite Reporter: Eric Helms <ehelms>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1.7CC: bkearney, ehelms
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-08 18:55:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Eric Helms 2016-05-03 14:49:13 UTC 
Description of problem:
In the Satellite 6.2 Beta, there appears to be a variety of strange happenings when a Pulp task is cancelled either manually or by restarting services.

1) The task appears to enter a paused/error state with Resume available that does nothing
2) Unlocking the task, then restarting services allows for the task to be resumed and re-enter paused/error state
3) The 'Skip' functionality in the dynflow console throws a 500