Errors about "No handlers found for logger" when running tox tests are problematic

[Amrith Kumar]

When I run tox (py27) the results include lines that indicate

No handlers found for logger ...

These lines are also non-deterministic because they occur in a portion of the test that runs multi-threaded.

The problem is that many of the tests (negative) cause the unit being tested to attempt to LOG an error but a logger hasn't been established.

I have a fix.

[Amrith Kumar (amrith)]

This includes lines like

No handlers could be found for logger "trove.guestagent.backup.backupagent"
No handlers could be found for logger "trove.guestagent.backup.backupagent"
No handlers could be found for logger "trove.cluster.models"
No handlers could be found for logger "trove.guestagent.strategies.storage.swift"

and maybe others!

[Amrith Kumar (amrith)]

No handlers could be found for logger "trove.conductor.manager"

The more CPU's you have, the more of these you seem to get ...

[Amrith Kumar (amrith)]

No handlers could be found for logger "trove.common.strategies.cluster.experimental.mongodb.api"

[OpenStack Infra (hudson-openstack)]

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

[Nikhil Manchanda (slicknik)]

This is related to unit tests and is not a blocker for Liberty-RC1.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/219544
Committed: https://git.openstack.org/cgit/openstack/trove/commit/?id=34ce70e299f57018b370ea0b8aa457f737f470b7
Submitter: Jenkins
Branch: master

commit 34ce70e299f57018b370ea0b8aa457f737f470b7
Author: Amrith Kumar <email address hidden>
Date: Sat Oct 17 18:29:57 2015 -0400

    Correct errors resulting in "No handlers ..." error message

    This is a checkin for the issue of having errors that read "No
    handlers could be found for logger X.Y.Z" when running tests. While
    being annoying, it is also a serious issue in that some times, the
    lack of logging masks errors in the tests. One such example is fixed
    in this chkin (see bug 1491093).

    Change-Id: I4066d226aefbd23248e88692db109d31f5c150e9
    Partial-Bug: #1491075
    Closes-Bug: #1491093