LDAP debug logging during unit tests brings us close to causing jenkins to fail our tests

[Henry Nash]

The Jenkins runs of our unit tests have a cap of 50Mb of log output..if we generate more than that, then it will fail out tests on the assumption that something is wrong. Our full run of our tests brings us perilously close already to this limit - primarily due to LDAP debug logging. We should switch off ldap debug logging for our unit tests.

[Henry Nash (henry-nash)]

This problem is currently stopping one of my patches passing (https://review.openstack.org/#/c/159675/), since I have created another LDAP scenario...and that pushes us over the 50Mb limit.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit d099aecb1af3e248b2411172e8306a54a576aa17
Author: Henry Nash <email address hidden>
Date: Tue Mar 3 16:30:54 2015 +0000

    Stop debug logging of Ldap while running unit tests

    Debug logging of Ldap generates at least 25Mb of log during
    a full run of unit tests. Combine this with other logging and
    we are close to blowing the 50Mb limit for a unit test run,
    meaning we cannot currently, for instance, add new Ldap tests.

    This patch changes the log level to INFO for Ldap.

    Change-Id: I36265212d402c96c33435fb0ff5c73acbcb42c89
    Closes-bug: 1427437