Comment 12 for bug 1021373

Reviewed: https://review.openstack.org/9534
Committed: http://github.com/openstack/nova/commit/4b89b4fd3665a6eaaa63911102070fd93f20f8bc
Submitter: Jenkins
Branch: stable/essex

commit 4b89b4fd3665a6eaaa63911102070fd93f20f8bc
Author: Eoghan Glynn <email address hidden>
Date: Tue Jul 10 12:11:28 2012 +0100

    Handle local & remote exceptions consistently.

    Related to LP 1021373.

    When the floating_ips quota threshold is exceeded, this occurs remotely
    in the networking service and hence is reported back to the API service
    over RPC, via a RemoteError wrapping the original QuotaError exception.

    Previously the handling of such RemoteErrors in the native API was
    inconsistent with exceptions raised locally within the API service.

    Now in both cases, we expose the exception explantion, status etc. in the
    response, if the exception type is declared as safe.

    This fix is not required on master, as the Folsom RPC failure deserialization
    logic renders it unnecessary.

    Change-Id: Icf7dcafd1f942f5d81d12587775d6ade4a176932