some API exception responses are not translated

[Mathew Odden]

There are some exception messages that are not being translated because they are caught and modified by the FaultWrapper
middleware class in the nova API. An example of this is the FloatingIpPoolNotFound exception from the neutron network API class.

Normally, any wsgi.Fault object would be translated, but FaultWrapper turns the exceptions into strings before we get a chance to translate it later.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/46585
Committed: http://github.com/openstack/nova/commit/c441af49814a57fdcc5482746bebbb6b80e46cd5
Submitter: Jenkins
Branch: master

commit c441af49814a57fdcc5482746bebbb6b80e46cd5
Author: Matt Odden <email address hidden>
Date: Fri Sep 13 09:50:18 2013 +0000

    Translate more REST API error messages

    There were a few exception messages that were not being
    translated because they were being wrapped and modified
    before being turned into wsgi.Fault objects by
    FaultWrapper. This adds some translation handling to
    the FaultWrapper so we can get these messages localized
    to the client's language specified in the Accept-Language
    header.

    Additionally adds a test to verfiy FaultWrapper is
    translating any exception messages that can be.

    fixes bug 1225226

    Change-Id: I3847cff0ac4b37f57eb04b27150c4e0d1ea23f29