Issue #2943: Cancelling a task group with no tasks throws a 404

Actions

Send by e-mail Copy link

Issue #2943

closed

Cancelling a task group with no tasks throws a 404

Added by jsherril@redhat.com about 6 years ago. Updated over 3 years ago.

Status:

CLOSED - WONTFIX

Priority:

Low

Assignee:

Category:

Sprint/Milestone:

Start date:

Due date:

Estimated time:

Severity:

1. Low

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Pulp 2

Sprint:

Quarter:

Description

If a task group such as applicability generation has no tasks, it throws an error. This is incredibly confusing to the point that i thought i was doing something wrong. A user would not expect that when given a task group id, canceling that task group would throw a 404.

To reproduce, generate applicability for a repository with no bound consumers, grab the task id, and attempt to cancel it.

Actions

Copy link

Updated by dkliban@redhat.com about 6 years ago

Priority changed from Normal to Low
Triaged changed from No to Yes

Task groups are not stored in a collection of their own. Task groups only exist as a field in the TaskStatus collection. As a result a task group with 0 tasks associated with it is the same as a task group that does not exist. Fixing this would require adding a separate collection for tracking task groups. This collection would need to store a group id at minimum.

Actions

Copy link

Updated by bmbouter over 4 years ago

Status changed from NEW to CLOSED - WONTFIX

Actions

Copy link

Updated by bmbouter over 4 years ago

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

Actions

Copy link