Bug 1041098

Summary:	[RFE][nova]: On successful Tempest test runs, we shouldn't have stacktraces in logs
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/no-stacktraces-in-logs
Whiteboard:	upstream_milestone_ongoing upstream_status_slow-progress
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:28:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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