OSAPI overLimit exceptions should use HTTP 413 error codes
Bug #785812 reported by
Dan Prince
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Troy Toman |
Bug Description
The HTTP return codes you get when you actually hit a quota limit are a weird mix. I get a 500 level error code when I hit a RAM limit (the one you are adding this this merge prop). Just for fun I tried another one for the personality limit and I got an HTTP 400 error code. Looking at the SPEC again it looks like we should actually be returning a HTTP 413 'overLimit' error code.
Related branches
lp:~troy-toman/nova/lp785812
- Brian Waldon (community): Approve
- Dan Prince (community): Approve
- Jay Pipes (community): Approve
-
Diff: 135 lines (+22/-12)8 files modifiedAuthors (+1/-0)
nova/api/openstack/common.py (+2/-1)
nova/api/openstack/create_instance_helper.py (+10/-3)
nova/api/openstack/server_metadata.py (+2/-1)
nova/quota.py (+1/-1)
nova/tests/api/openstack/test_image_metadata.py (+2/-2)
nova/tests/api/openstack/test_server_actions.py (+2/-2)
nova/tests/api/openstack/test_server_metadata.py (+2/-2)
Changed in nova: | |
assignee: | nobody → Titan (rackspace-titan) |
Changed in nova: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in nova: | |
assignee: | Dan Prince (dan-prince) → Troy Toman (troy-toman) |
status: | Confirmed → In Progress |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
milestone: | none → diablo-4 |
Changed in nova: | |
milestone: | diablo-4 → 2011.3 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
@Titan team: are you working on that, or should we unassign you to let someone else potentially have a try at it ?