yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #47512
[Bug 1553319] Re: When CPU metric collection fails, stack trace not in nova logs
Reviewed: https://review.openstack.org/288750
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=aef7a3dab112690e5172d137decb93dc28056471
Submitter: Jenkins
Branch: master
commit aef7a3dab112690e5172d137decb93dc28056471
Author: Joe Cropper <jwcroppe@xxxxxxxxxx>
Date: Fri Mar 4 15:22:30 2016 -0600
Dump metric exception text to logs
This patch simply adds the exception text to the logs so that we don't
lose the troubleshooting data. Without this patch, it's much more
difficult to troubleshoot when something goes wrong as the root
exception text is garbled up and lost.
Change-Id: Ib432fddc9b31fb6f906f6828d52098c9dd059aa2
Closes-Bug: 1553319
** Changed in: nova
Status: In Progress => 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/1553319
Title:
When CPU metric collection fails, stack trace not in nova logs
Status in OpenStack Compute (nova):
Fix Released
Bug description:
When the resource tracker tries to collect metric data, if something
goes wrong, the stack trace isn't shown and it masks the underlying
problem and makes debug difficult.
For example, here's the message you see...
2016-03-04 13:45:02.582 31225 WARNING nova.compute.resource_tracker
[req-141a8c26-fa98-470d-accb-97b15bf98d70 - - - - -] Cannot get the
metrics from...
...and no stack trace.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1553319/+subscriptions
References