Clearer API Error Responses
Currently the cinder api and other openstack apis when things are successful will return a JSON/XML response with the requested information, or the result of modifying a resource. Currently if something was to go wrong in these calls, an accepted RFC HTTP response code is returned. For complex calls like quota exceeded [1] there are a number of things that can go wrong where a 500 error is unhelpful, especially when the end user doesn't have access to the API logs to debug the issue further. Returning a JSON error response in the body instead would allow developers writing clients (python-
[1] - https:/
Blueprint information
- Status:
- Complete
- Approver:
- John Griffith
- Priority:
- High
- Drafter:
- Mike Perez
- Direction:
- Approved
- Assignee:
- Mike Perez
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Mike Perez
- Completed by
- Mike Perez
Related branches
Related bugs
Sprints
Whiteboard
Need to get v2 blueprint out first: https:/
After doing an audit I have found this commit taking care of the reported issues:
https:/
Work Items
Dependency tree
* Blueprints in grey have been implemented.