auth_token needs logging enabled

HI Joseph,

Is this the reason for the Improper result when either of service_token OR service_endpoint is not set. E.g. I get the msg:
" No handlers could be found for logger "keystoneclient.v2_0.client"
when I unset the SERVICE_ENDPOINT.

deepak@deepak-devvm:~/devstack$ keystone --token admintoken tenant-list
+----------------------------------+--------------------+---------+
| id | name | enabled |
+----------------------------------+--------------------+---------+
| 0427c8663a744e3e9fb0ae3e9dc481c7 | admin | True |
| 18c5ced234e341ab9dc8d826411ca3ef | dg2 | True |
| 99edfffc78f14ca2b77680d574afe196 | demo | True |
| ddaa5907076b44fdb423986650c4068e | invisible_to_admin | True |
+----------------------------------+--------------------+---------+

deepak@deepak-devvm:~/devstack$ unset SERVICE_ENDPOINT
deepak@deepak-devvm:~/devstack$ keystone --token admintoken tenant-list
No handlers could be found for logger "keystoneclient.v2_0.client"
+----------------------------------+-------+---------+
| id | name | enabled |
+----------------------------------+-------+---------+
| 0427c8663a744e3e9fb0ae3e9dc481c7 | admin | True |
| 99edfffc78f14ca2b77680d574afe196 | demo | True |
+----------------------------------+-------+---------+

No, it's unrelated - the error message you're getting it no python logging handlers in the keystone client code to forward log messages. A root handler enabled in a program should generally take care of that.

This is logging in the keystone.middleware.auth_token which should be applicable to the owning application (nova, glance, etc) so that if the middleware needs or wants to send out a debug log (i.e. to indicate a reason for failure to the system owner), it can. RIght now, there is no logging happening in the middleware.

Thanks Joseph,
So, whats the correct way to resolve the issue.
  a. Manually enable the handler in the client code ( using cmd line probably ) ?
  b. It should have been enabled by the code and we should raise a bug.

I am talking about my issue here, ( to be clear )

Deepak - please open a separate bug or open a "Question" in Keystone and let's discuss it there. I'd rather than confuse this bug/issue with unrelated discussion.

Marking as fix committed based on the auth_token rewrite last week