Actions
Issue #1070
closed202 is returned on DELETE bind repo for consumer when parameter is not valid
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.7.0 Beta
Platform Release:
OS:
RHEL 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:
Description
If a user makes a typo and prints option instead of optionS, 202 will be returned. I expect 400: invalid parameter
>> rpm -qa pulp-server
pulp-server-2.7.0-0.3.beta.el7.noarch
>> pulp-consumer rpm bind --repo-id=zoo_repoBind tasks successfully created:
Task Id: be03d103-44b2-47e7-b01e-3e5d86a5c090
>> curl -i -H "Accept: application/json" -H "WebFrameworkSwitch: webpy" -X DELETE -k -u admin:admin -d '{"invalid":"yes"}' "https://localhost/pulp/api/v2/consumers/maruska/bindings/zoo_repo/yum_distributor/"
HTTP/1.1 202 ACCEPTED
Date: Sat, 27 Jun 2015 13:40:59 GMT
Server: Apache/2.4.6 (Red Hat Enterprise Linux) OpenSSL/1.0.1e-fips mod_wsgi/3.4 Python/2.7.5
Content-Encoding: utf-8
Content-Length: 447
Content-Type: application/json
{"spawned_tasks": [{"_href": "/pulp/api/v2/tasks/49927a76-29cc-4af7-9fc6-ffc22dea11ab/", "task_id": "49927a76-29cc-4af7-9fc6-ffc22dea11ab"}], "result": {"notify_agent": true, "repo_id": "zoo_repo", "deleted": false, "_ns": "consumer_bindings", "distributor_id": "yum_distributor", "consumer_id": "maruska", "consumer_actions": [], "binding_config": {}, "_id": {"$oid": "558ea7e1e512ed777daefd80"}, "id": "558ea7e1e512ed777daefd80"}, "error": null}
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 5 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