Excessive logging due to defaults being unset in tests

Bug #1340970 reported by Morgan Fainberg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Medium
Morgan Fainberg

Bug Description

Keystone logs from tests tend to be excessively large due to the default log levels not being set.
This can occasionally cause logs to exceed the 50MB limit (infra) on a gate/check job.

Changed in keystone:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Morgan Fainberg (mdrnstm)
milestone: none → juno-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to keystone (master)

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

Changed in keystone:
status: Confirmed → In Progress
tags: added: test-improvement
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to keystone (master)

Reviewed: https://review.openstack.org/106496
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=d4aa4c895f52ff4e99ff785bd31da34ada038e7c
Submitter: Jenkins
Branch: master

commit d4aa4c895f52ff4e99ff785bd31da34ada038e7c
Author: Morgan Fainberg <email address hidden>
Date: Fri Jul 11 16:03:17 2014 -0500

    Make sure unit tests set the correct log levels

    Unit tests appear to not set the expected logging levels so
    a number of modules will log excessivly (e.g. ISO8601).

    This change ensures the base test classe sets the correct logging
    levels (in the same way as the openstack.common.log module).

    Change-Id: Ic11b7adee5f27f71094b4ef2b4a635f78f83cba8
    Closes-Bug: #1340970

Changed in keystone:
status: In Progress → Fix Committed
Changed in keystone:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in keystone:
milestone: juno-2 → 2014.2
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.