pecan exception handler inconsistent with legacy exception handler

[Kevin Benton]

the exception handler for pecan is missing logic for handling NotImplemented error, language translation, and error logging that is present in the legacy framework, which results in inconsistent error results for the user depending on the API used.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/319015
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a1c194cf060b2d563beb36261c7702950446756f
Submitter: Jenkins
Branch: master

commit a1c194cf060b2d563beb36261c7702950446756f
Author: Kevin Benton <email address hidden>
Date: Fri May 13 14:29:18 2016 -0700

    Make exception translation common and add to pecan

    This moves the exception translation logic from the
    legacy api.v2.resource module to a common module and
    re-uses it from pecan to bring consistency to the
    way language and exception translation is handled
    between the two.

    This also adjusts the policy enforcement hook to correctly
    handle the unsupported method case since 'after' hooks
    are executed after 'on_error' hooks that return an exception.

    Closes-Bug: #1583844
    Change-Id: If3c2d8c94ca6c1615f3b909accf0f718e320d1c2

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/neutron 9.0.0.0b1 development milestone.