InvalidQuotaValue should be 400 or 403 rather than 409

Bug #1210274 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Undecided
Unassigned

Bug Description

The neutron.common.exceptions.InvalidQuotaValue exception extends Conflict which is a 409 status code but that doesn't really make sense for this exception. I'd say it should be a BadRequest (400) but the API docs list possible response codes for quota extension operations as 401 or 403:

http://docs.openstack.org/api/openstack-network/2.0/content/Update_Quotas.html

In this case I'd say it's more of a 403 than a 409. Regardless, 409 isn't even in the API doc for the quota extension.

Tags: api
Aaron Rosen (arosen)
tags: added: api
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/40969

Changed in neutron:
assignee: nobody → Matt Riedemann (mriedem)
status: New → In Progress
Changed in neutron:
assignee: Matt Riedemann (mriedem) → Abhishek Talwar (abhishek-talwar)
Changed in neutron:
assignee: Abhishek Talwar (abhishek-talwar) → nobody
Revision history for this message
Rossella Sblendido (rossella-o) wrote :

Marking this as invalid, looking at the comments in the proposed code review it seems that 409 is OK after all

Changed in neutron:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.