Not all exception information is propagated through API

[Christopher Yeoh]

The python neutron client for the V2 API expects the neutron API to send information back such as the type and detail of the exception the body of the message (serialized as a dict). See exception_handler_v20 in client.py. However, the neutron v2 api only returns the exception message. This means that the client can only propagate up a generic NeutronClientException exceptions rather than more specific ones related to the actual problem.

All of the necessary information is present in the v2 api resource class at the point the webob exception is raised to include at least the type of the exception (detail appears not to be used in neutron exceptions) so the format of the message returned should be changed to include a type field and a message field rather than just the message.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/47351
Committed: http://github.com/openstack/neutron/commit/20b97388efcc3540066ca7743c761c1ec899dd2c
Submitter: Jenkins
Branch: master

commit 20b97388efcc3540066ca7743c761c1ec899dd2c
Author: Oleg Bondarev <email address hidden>
Date: Thu Sep 19 15:07:23 2013 +0400

    Send proper exception info as expected by the neutron client

    The python neutron client for the V2 API expects the neutron API
    to send information back such as the type and detail of the exception
    in the body of the message

    Change-Id: I9486d757258c4be72799c41102babe1f7923121c
    Closes-bug: #1226400