Client should be able to process the pecan constructed exceptions in the response body

[Vladyslav Drok]

Right now, the following problem exists:

ironic node-validate 123~123
Bad Request (HTTP 400)

The error text is ignored, as this is an exception raised by pecan from node controller _lookup method. Unlike wsme exceptions, the response body with this exception looks like this:

{"error_message": "{\"code\": 400, \"description\": \"Expected a logical name or UUID but received 123~123.\", \"title\": \"Bad Request\"}"}

Right now, the description field is ignored and client is looking for faultstring field in the response.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/364566

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/364566
Committed: https://git.openstack.org/cgit/openstack/python-ironicclient/commit/?id=fbcaf92521280f5c1cdfb447a17eb2c5b3059ba7
Submitter: Jenkins
Branch: master

commit fbcaf92521280f5c1cdfb447a17eb2c5b3059ba7
Author: Vladyslav Drok <email address hidden>
Date: Fri Sep 2 00:31:24 2016 +0300

    Print pecan exceptions properly

    Exceptions raised by pecan (for example the ones happening in _lookup
    methods of ironic controllers) are not properly handled, as the
    fields that contain the error details are different from wsme raised
    exceptions. This change fixes it.

    Closes-Bug: #1619471
    Change-Id: I023870ed97d3e97df8ae67e7cec97d6fbf355e79

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-ironicclient 1.12.0 release.