Bug 1042570 - [RFE][neutron]: Log as ERROR only for conditions requiring operator attention
Summary: [RFE][neutron]: Log as ERROR only for conditions requiring operator attention
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/neut...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 00:23 UTC by RHOS Integration
Modified: 2015-11-20 19:36 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description RHOS Integration 2013-12-13 00:23:21 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/log-only-exceptional-conditions-as-error.

Description:

There is a tempest blueprint (https://blueprints.launchpad.net/tempest/+spec/fail-gate-on-log-errors) that proposes to start failing gate jobs if ERROR appears in the logs unexpectedly.  There is a whitelist so that expected error conditions for a given project don't trigger failure, but at present Neutron logs so many things as ERROR that whitelisting is not feasible.  A cleanup effort is required to reduce the incidence of logging as ERROR to cases that would conceivably require operator attention.  Ideally the number of such conditions would be small enough that whitelisting wouldn't mask actual problems.

Tempest is going to start outputting all ERROR log lines in the gate jobs for Neutron so we can start eliminating the unnecessary logging to the point where whitelisting is possible.  Once we're satisfied with the whitelisting, Tempest can start failing jobs that produce errors that aren't whitelisted.

Specification URL (additional information):

None


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