Actions
Issue #4471
closed
Pulp returns 200 when it fails to create rpm content
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 49
Quarter:
Description
Steps to reproduce:
$ echo "blah" > foo-4.1-1.noarch.rpm
$ http --form POST http://localhost:8000/pulp/api/v3/artifacts/ file@./foo-4.1-1.noarch.rpm
$ http POST http://localhost:8000/pulp/api/v3/content/rpm/packages/ relative_path=foo.rpm _artifact="/pulp/api/v3/artifacts/1/" filename=foo-4.1-1.noarch.rpm
The response correctly shows an error ("RPM file cannot be parsed for metadata.") but the http status code is 200.
Related issues
Added by ppicka about 5 years ago
Updated by ppicka about 5 years ago
- Status changed from NEW to POST
Updated by ppicka about 5 years ago
- Status changed from POST to MODIFIED
Applied in changeset 786308c80b8f0da3841ccd4af4a90f4cf6189de6.
Updated by bherring about 5 years ago
- Copied to Issue #4537: Pulp returns 200 when it fails to create rpm content added
Updated by ttereshc over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Change return status
When RPM file is not parsable return 406 (Not Acceptable) as rpm cannot be accepted due to metadata parse failed.
closes: #4471 https://pulp.plan.io/issues/4471
Signed-off-by: Pavel Picka ppicka@redhat.com