pecan: nova notifier breaks on errors

[Kevin Benton]

The nova notifier code always assumes there is a previous resource on a PUT action. However, this is not the case in scenarios where an update is attempted on an object that doesn't exist (in which case a 404 will be raised). The current nova code was breaking the 404 by failing in the notification code.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit 19348ecd6eefdab5e7ba6cabbeff1d3e124bb00f
Author: Kevin Benton <email address hidden>
Date: Mon Mar 14 07:43:50 2016 -0700

    Pecan: skip all notifications on failures

    If there was a bad status code, none of the notification
    logic should attempt to process. A bad status code means
    that the assumptions the notification code makes about
    original resources being present may not be true.

    This also fixes the exception translator so the correct
    status code is set by the hook on exceptions that have
    a fault map entry.

    Closes-Bug: #1557516
    Change-Id: Ibff419e7caa6de422f04eb1e43fd2aed304bdd97

[Doug Hellmann (doug-hellmann)]

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