Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #6465

closed

cancelling a 'complete' task returns strange result

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

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
mdellweg
Category:
-
Sprint/Milestone:
3.4.0
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'.

Actions
Send by e-mail Copy link

Also available in: Atom PDF