Bug 1332609 - What happens when a Pulp task is cancelled?
Summary: What happens when a Pulp task is cancelled?
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.1.7
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-03 14:49 UTC by Eric Helms
Modified: 2017-02-08 18:55 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-08 18:55:40 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.