conductor logs expected exceptions

[aeva black]

RPC methods may return an exception from the ConductorManager as an expected means to inform the API of an error. Such expected exceptions should not be logged within the conductor -- otherwise the log will be meaningless as real (unexpected) exceptions go unnoticed.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/80022
Committed: https://git.openstack.org/cgit/openstack/ironic/commit/?id=fc490d490ac7704c4654395fb21d498b9f1c7f4e
Submitter: Jenkins
Branch: master

commit fc490d490ac7704c4654395fb21d498b9f1c7f4e
Author: Devananda van der Veen <email address hidden>
Date: Wed Mar 12 10:40:03 2014 -0700

    Suppress conductor logging of expected exceptions

    RPC methods may return an exception from the ConductorManager as an
    expected means to inform the API of an error. Such expected exceptions
    should not be logged within the conductor -- otherwise the log will be
    overflowing and real (unexpected) exceptions will go unnoticed.

    This patch adds a decorator to the RPC methods in ConductorManager to
    suppress logging of expected exceptions, while still passing them back
    to the API.

    Co-Authored-By: David Shrewsbury <email address hidden>

    Change-Id: Ic3107a9af6afeb2a9e772ca0ce0acc45dbc182cb
    Closes-bug: #1291509