Project

Profile

Help

Story #832

closed

As a user, I can cancel all running tasks using API

Added by dkliban@redhat.com about 7 years ago. Updated almost 3 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

When trying to diagnose problems, a user often needs to be able to cancel all running tasks. This requires a user to look through the list of tasks and determine which ones are actually running or waiting. Only then can a user start issuing individual requests for each task. Affording a user to cancel all tasks in RUNNING or WAITING state with a single request would be a much better user experience. This story is only half of the work needed to make the experience truly better. The second story describes how pulp-admin needs to be extended to make use of the new API endpoint. The acceptance criteria for this story include the following:

- '/pulp/api/v2/tasks' API endpoint needs to accept a DELETE request. This action should cancel all tasks in RUNNING or WAITING state
- Documentation about the API
- Release notes about the new feature


Related issues

Blocks Pulp - Story #837: As a user, I can cancel all running and waiting tasks using pulp-adminCLOSED - WONTFIX

Actions
Actions #1

Updated by dkliban@redhat.com about 7 years ago

  • Description updated (diff)
Actions #2

Updated by dkliban@redhat.com about 7 years ago

  • Description updated (diff)
Actions #3

Updated by dkliban@redhat.com about 7 years ago

  • Description updated (diff)
Actions #4

Updated by bmbouter about 7 years ago

How can this be done without adding a dedicated endpoint for this one operation?

Actions #5

Updated by dkliban@redhat.com about 7 years ago

  • Description updated (diff)
Actions #6

Updated by bmbouter about 7 years ago

FYI, our upgrade instructions usually don't tell users to cancel all running tasks.

Also, this can be broken into two stories: first the API, then the CLI. Since it can be broken up I think it should. They should have a depends on relationship.

Lastly, using the DELETE sounds good, but having a DELETE on the generic task sound a little scary. What about a DELETE on /pulp/api/v2/tasks/* or /pulp/api/v2/tasks/all-tasks

Using either * or 'all-tasks' won't collide with any other task because all of our tasks are identified by uuid. I'm not 100% sure that this better. I'd like to have a third opinion given.

Actions #7

Updated by dkliban@redhat.com about 7 years ago

  • Subject changed from As a user, I can cancel all running tasks to As a user, I can cancel all running tasks using API
  • Description updated (diff)
Actions #8

Updated by dkliban@redhat.com about 7 years ago

  • Blocks Story #837: As a user, I can cancel all running and waiting tasks using pulp-admin added
Actions #9

Updated by mhrivnak about 7 years ago

  • Tags deleted (Sprint Candidate)
Actions #10

Updated by amacdona@redhat.com about 3 years ago

  • Tags Pulp 3 added
Actions #11

Updated by amacdona@redhat.com about 3 years ago

  • Sprint/Milestone set to 58
Actions #12

Updated by bmbouter about 3 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #13

Updated by bmbouter about 3 years ago

  • Tags deleted (Pulp 3)
Actions #14

Updated by bmbouter almost 3 years ago

  • Sprint/Milestone deleted (58)

Also available in: Atom PDF