API formatting of errors and exceptions
Currently any API request that results in an error response results in an error message which is one of:
- a stack trace
- a generic http error response which hides the original message
Error responses should exhibit the following:
- an appropriate HTTP response code set
- a message which is clear and helpful to the user
- where appropriate, some machine-parsable reference to where in the template the source of the error is (parameter name for validation error, resource name for a resource error, etc)
python-heatclient and horizon should display any message and make use of any reference to template elements.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Baker
- Priority:
- Medium
- Drafter:
- Steve Baker
- Direction:
- Approved
- Assignee:
- Jianing Yang
- Definition:
- Approved
- Series goal:
- Accepted for havana
- Implementation:
- Implemented
- Milestone target:
- 2013.2
- Started by
- Steve Baker
- Completed by
- Steven Hardy
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
make heat-api return a parsable error
Gerrit topic: https:/
Addressed by: https:/
remove remote_error and corresponding try...catches.
Addressed by: https:/
Add unittests for faultwrap middleware
Gerrit topic: https:/
Addressed by: https:/
Use openstack rpc functions to generate _Remote exceptions