Successful full gate jobs show ERRORs and stacktraces

Bug #1079211 reported by David Kranz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Fix Released
Low
Brian Waldon
Grizzly
Fix Released
Low
Brian Waldon

Bug Description

Here are the log files that contain errors even though all of the tempest tests passed. There are still flaky failures in this test suite and it is much harder to diagnose when there are spurious ERRORs when nothing is wrong. We should be failing the gating tests if ERROR shows up in the log. This is also an issue for system monitoring. An ERROR in a log file should mean there is an OpenStack bug, or an operator configuration error.

g-api
g-reg

Revision history for this message
David Kranz (david-kranz) wrote :
Brian Waldon (bcwaldon)
Changed in glance:
status: New → Triaged
importance: Undecided → Low
milestone: none → grizzly-1
assignee: nobody → Brian Waldon (bcwaldon)
Brian Waldon (bcwaldon)
Changed in glance:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to glance (master)

Fix proposed to branch: master
Review: https://review.openstack.org/16347

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/16349

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to glance (master)

Reviewed: https://review.openstack.org/16347
Committed: http://github.com/openstack/glance/commit/e063993246704caea9d19ea9cc975921dcdff78a
Submitter: Jenkins
Branch: master

commit e063993246704caea9d19ea9cc975921dcdff78a
Author: Brian Waldon <email address hidden>
Date: Fri Nov 16 15:51:54 2012 -0800

    Stop logging all registry client exceptions

    Not all exceptions need to be logged as ERROR in the glance-api
    log when - for instance, a user asking for an image that does not
    exist doesn't mean an ERROR actually occurred. This logs the exception
    name at INFO level. An ERROR won't be logged at all, even in
    the case of a 500-level response from glance-registry. An operator
    would be alerted with an ERROR log in the glance-registry log in that
    case.

    Fixes bug 1079211.

    Change-Id: Ie2bba3105f8d9f3de97bc50132fb046baf710a90

Changed in glance:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Reviewed: https://review.openstack.org/16349
Committed: http://github.com/openstack/glance/commit/d576f897bcf4877a478ced10af05e3c79455e02a
Submitter: Jenkins
Branch: master

commit d576f897bcf4877a478ced10af05e3c79455e02a
Author: Brian Waldon <email address hidden>
Date: Fri Nov 16 16:23:34 2012 -0800

    Audit error logging

    Reduce log level from error to info/debug in several cases
    where users do something silly. The operator of Glance
    does not need to be alerted with an ERROR log in these
    cases.

    Fixes bug 1079211.

    Change-Id: I09d86c8727530cf58f22446493ef9c4789d5d6cb

Thierry Carrez (ttx)
Changed in glance:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.