error responses do not comply with OpenStack API WG guidelines

Bug #1676437 reported by Thomas Maddox
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
craton
New
Undecided
Unassigned

Bug Description

Discussed on this review: https://review.openstack.org/#/c/447580.

Please see here for the suggested guideline: https://specs.openstack.org/openstack/api-wg/guidelines/errors.html.

Currently we're returning errors that look like:

{
    "message": "<error message>",
    "code": 400
}

This is not robust enough to meet the needs of clients, especially when the request generates several errors that we wish to communicate in a uniform, machine-friendly way.

description: updated
Changed in craton:
milestone: none → v0.2.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers