API formatting of errors and exceptions

Registered by Steve Baker on 2013-07-04

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:
milestone icon 2013.2
Started by
Steve Baker on 2013-07-17
Completed by
Steven Hardy on 2013-09-03

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bug/1158598,n,z

Addressed by: https://review.openstack.org/36678
    make heat-api return a parsable error

Gerrit topic: https://review.openstack.org/#q,topic:bp/exception-formatting,n,z

Addressed by: https://review.openstack.org/37908
    remove remote_error and corresponding try...catches.

Addressed by: https://review.openstack.org/40798
    Add unittests for faultwrap middleware

Gerrit topic: https://review.openstack.org/#q,topic:exception-formatting,n,z

Addressed by: https://review.openstack.org/40814
    Use openstack rpc functions to generate _Remote exceptions

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.