Bug 1015290 - importer delete has empty response
importer delete has empty response
Status: CLOSED NOTABUG
Product: Pulp
Classification: Community
Component: API/integration (Show other bugs)
Master
Unspecified Unspecified
unspecified Severity low
: ---
: 2.3.0
Assigned To: Barnaby Court
pulp-qe-list
: Triaged
Depends On:
Blocks: 965283
  Show dependency treegraph
 
Reported: 2013-10-03 16:06 EDT by Michael Hrivnak
Modified: 2013-10-07 13:55 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-07 13:55:43 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Hrivnak 2013-10-03 16:06:42 EDT
Description of problem:

When using the REST API to delete an importer from a repo, the response body is empty.


Version-Release number of selected component (if applicable):
master

How reproducible:
always

Steps to Reproduce:
1. $ pulp-admin rpm repo create --repo-id=foo
2. using pic...
3. pic.DELETE('/pulp/api/v2/repositories/foo/importers/yum_importer/')

Actual results:

Response Body
null
(200, None)


Expected results:

a task ID and other taks-related things.


Additional info:

The importer does get deleted, so it's just the HTTP response that is broken.
Comment 1 Barnaby Court 2013-10-07 11:48:28 EDT
This returns 200 and no task body in the case where the delete happened immediately.  If the delete does not happen immediately a task body will be returned.

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