config-fix-sqlalchemy-pool-enable-logging

Bug #1455493 reported by John Wood
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Barbican
Fix Released
Medium
John Wood

Bug Description

The 'sql_pool_logging' field recently added to the barbican-api.conf file does not control SQLAlchemy pool logging. Rather debug statements from the pool classes are output always regardless of the setting.

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

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

Changed in barbican:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to barbican (master)

Reviewed: https://review.openstack.org/183520
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=6a10ec71f50b85c5454474b5127473402789cec1
Submitter: Jenkins
Branch: master

commit 6a10ec71f50b85c5454474b5127473402789cec1
Author: jfwood <email address hidden>
Date: Fri May 15 08:31:04 2015 -0500

    Fix the sql_pool_logging config attribute

    The 'sql_pool_logging' config field is a boolean value, but it was
    being treated as a text value in repositories.py, so any value
    supplied to it was treated as a non-None condition which enabled
    SQLAlchemy pool logging always. This CR changes this field to the
    proper boolean type.

    Change-Id: If2c1471d5a3b1fca4ac5033754d05b386fb0cbf5
    Closes-Bug: #1455493

Changed in barbican:
status: In Progress → Fix Committed
Changed in barbican:
importance: Undecided → Medium
Changed in barbican:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in barbican:
milestone: liberty-1 → 1.0.0
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.