Reviewed: https://review.openstack.org/51075 Committed: http://github.com/openstack/nova/commit/b64ea7c2cb76c476a178deeed6ab9e83676faf05 Submitter: Jenkins Branch: milestone-proposed
commit b64ea7c2cb76c476a178deeed6ab9e83676faf05 Author: Dan Smith <[email protected]> Date: Tue Oct 1 12:12:13 2013 -0700 Avoid spamming conductor logs with object exceptions Conductor's logs should include tracebacks only when something unexpected happened, which is why we have the client_exceptions() decorator. The object_action() and object_class_action() methods are used for direct remoting of object methods, and thus really should forward *any* exception to the client. This patch does that, and also adds missing tests for these two methods to verify the normal and exception-wrapped behavior. Closes-bug: #1233789 Closes-bug: #1084706 Change-Id: I505462fa429a6aa68e7b8a08ec2b704bf18d029c (cherry picked from commit 3a5e1faee04671f2e88b28d805b191b480054254) ** Changed in: nova Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1233789 Title: Object actions via conductor will result in verbose exception logging Status in OpenStack Compute (Nova): Fix Released Bug description: See http://logs.openstack.org/87/44287/9/check/gate-tempest-devstack- vm-full/c3a07eb/logs/screen-n-cond.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1233789/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
