No handlers could be found for logger "keystoneclient..."

[Joseph Heck]

most commands result in this line being printed: 'No handlers could be found for logger "keystoneclient.v2_0.client"'

[OpenStack Infra (hudson-openstack)]

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

[Dolph Mathews (dolph)]

Raised the priority on this bug now that middleware.auth_token has been moved into keystoneclient.

[Chmouel Boudjnah (chmouel)]

is that for swift ? because we have fixed it here :

https://review.openstack.org/#/c/18446/

[Dolph Mathews (dolph)]

Chmouel: in general, however I've lowered the priority again since auth_token can be handed an existing logger (thanks!)

This still affects CLI usage

[ZhiQiang Fan (aji-zqfan)]

so does keystoneclient.middleware.auth_token

[ZhiQiang Fan (aji-zqfan)]

sorry for it, actually i already have a fix in my local branch, but seems more problems are rising when test, especially huge amount of screen logs when running test, (mainly printed by middleware.auth_token module) and i already upload other patch to fix those problem first

sorry again, wish i have more time to working on openstack

[Openstack Gerrit (openstack-gerrit)]

Reviewed: https://review.openstack.org/88097
Committed: https://git.openstack.org/cgit/openstack/python-keystoneclient/commit/?id=59daf4bf02b60a523d7f68004b75316086e91d2a
Submitter: Jenkins
Branch: master

commit 59daf4bf02b60a523d7f68004b75316086e91d2a
Author: Brant Knudson <email address hidden>
Date: Wed Apr 16 17:07:03 2014 -0500

    CLI always configures logging

    When the keystone CLI wound up logging something and --debug
    wasn't set, a message was printed that 'No handlers could be
    found for logger <whatever>'. This is because Python logging
    was only configured when the --debug option was set.

    This change makes it so that logging is always configured. If
    --debug is used then the level is DEBUG and if it's not used
    then the level is WARNING.

    Change-Id: Ib01d1072acff0d6ede468b0ecab4f871459014ee
    Closes-Bug: #936404