Actions
Issue #6465
closedcancelling a 'complete' task returns strange result
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 72
Quarter:
Description
$ http PATCH :/pulp/api/v3/tasks/f0f054b1-3b50-4c9a-9908-90e8422ab8f8/ state=canceled HTTP/1.1 200 OK Allow: GET, PATCH, DELETE, HEAD, OPTIONS Connection: Keep-Alive Content-Length: 11 Content-Type: application/json Date: Tue, 07 Apr 2020 20:45:39 GMT Keep-Alive: timeout=5, max=10000 Server: gunicorn/20.0.4 Vary: Accept,Cookie X-Frame-Options: SAMEORIGIN { "name": "" }
I expect to get the task with a state set to 'complete'.
Updated by fao89 over 4 years ago
- Triaged changed from No to Yes
- Sprint set to Sprint 70
Updated by mdellweg over 4 years ago
I would expect to receive an error ("409 conflict" comes to mind.) because the requested action to cancel that task will not be performed.
Updated by mdellweg over 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to mdellweg
Updated by pulpbot over 4 years ago
- Status changed from ASSIGNED to POST
Added by mdellweg over 4 years ago
Updated by mdellweg over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulpcore|310bd09d7b1026f22130aaa5cfdbc37ec590d75b.
Updated by dkliban@redhat.com over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Fix response when trying to cancel a completed task
fixes #6465 https://pulp.plan.io/issues/6465