← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1148516] Re: include more information when logging rpc call exceptions

 

looks like this was fixed

** Changed in: nova
       Status: Triaged => 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/1148516

Title:
  include more information when logging rpc call exceptions

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When an rpc exception happens it used to show a useless traceback in
  the log: http://logs.openstack.org/22610/2/gate/gate-tempest-devstack-
  vm-full/6278/logs/screen-n-cpu.txt.gz

  This other bug removed the traceback:
  https://bugs.launchpad.net/nova/+bug/1137994

  ----

  Some openstack installation administrators would like to have a useful
  traceback when rpc calls fail in order to debug the installation.

  However as bug #1137994 notes; some rpc calls are expected to fail and
  would just generate noise in the logs if they logged these tracebacks.

  ----

  We propose having optional tracebacks, and that the traceback's have
  useful information in them.

  The option will most likely come from a parameter to the rpc call
  method, or an extra special attribute in the message; eg
  {'_disable_exception_logging': True}.

  The default would be on, however for those methods that expect a
  failure, they would be disable logging of exceptions and log what they
  need themselves. That way the caller can decide if they want logging.

  The traceback logged will show the methods that led down to the call
  being initiated, and the rpc topic (if available) and the method
  called.

  ----

  Fixing in oslo-incubator: https://review.openstack.org/#/c/23508/

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1148516/+subscriptions