docs: using the correct format and real world example for fault message

This patch corrects the fault message format, and use an example which
existed in the real world.

blueprint complete-todo-in-api-concept-doc

Change-Id: I76706cca5a9fdcfa6c3e2c9d08aa8f94fb9471d8
This commit is contained in:
He Jie Xu
2015-11-22 22:32:01 +08:00
committed by Ken'ichi Ohmichi
parent 4a9133d464
commit 10559e91e1

View File

@@ -64,10 +64,9 @@ information about the fault in the body of the response.
.. code:: .. code::
{ {
"computeFault":{ "itemNotFound":{
"code":500, "code": 404,
"message":"Fault!", "message":"Aggregate agg_h1 could not be found."
"details":"Error Details..."
} }
} }
@@ -126,10 +125,10 @@ created timestamp that specify when the fault occurred.
"id": "52415800-8b69-11e0-9b19-734f216543fd" "id": "52415800-8b69-11e0-9b19-734f216543fd"
}, },
"fault" : { "fault" : {
"code" : 404, "code" : 500,
"created": "2010-08-10T11:59:59Z", "created": "2010-08-10T11:59:59Z",
"message" : "Could not find image 52415800-8b69-11e0-9b19-734f6f007777", "message": "No valid host was found. There are not enough hosts available.",
"details" : "Fault details" "details": [snip]
}, },
"links": [ "links": [
{ {