Bug 1041098 - [RFE][nova]: On successful Tempest test runs, we shouldn't have stacktraces in logs
Summary: [RFE][nova]: On successful Tempest test runs, we shouldn't have stacktraces i...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_ongoing upstream_s...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 13:38 UTC by RHOS Integration
Modified: 2015-03-19 17:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:28:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 13:38:07 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/no-stacktraces-in-logs.

Description:

If Nova is acting normally, we shouldn't have stack traces in our logs. It will make problem determination by admins and developers unnessessarily hard as they'll have to mentally filter out important vs. "always happens" stack traces. We should enforce this by making gate fail if after we've running all the tests successfully we find stack traces in the logs.

Specification URL (additional information):

None
Note You need to log in before you can comment on or make changes to this bug.