While running through the Folsom getting started guide, this message is emitted from the keystone client application. The first command from the guide that demonstrates this problem is: [root@rhel ~(keystone_admin)]# keystone user-list No handlers could be found for logger "keystoneclient.v2_0.client" +----------------------------------+-------+---------+-------+ | id | name | enabled | email | +----------------------------------+-------+---------+-------+ | 12ab8ebd87bc496c93744bcabb40300f | admin | True | | +----------------------------------+-------+---------+-------+ It occurs with many other commands, as well. Even if this message may technically be just an eye-sore, it will be alarming for users since it looks like an error has occurred. It should be fixed so that this never comes up and causes false alarm.
Related upstream review https://review.openstack.org/#/c/18129/
*** Bug 888244 has been marked as a duplicate of this bug. ***
*** Bug 889308 has been marked as a duplicate of this bug. ***
Runs fine for me - how do I reproduce this? [root@ykaul-os-horizon ~]# source ~/keystonerc_admin [root@ykaul-os-horizon ~(keystone_admin)]$ keystone user-list +----------------------------------+--------+---------+------------------+ | id | name | enabled | email | +----------------------------------+--------+---------+------------------+ | 6d3e685e0fd34060bc9e47bda8111abc | cinder | True | cinder@localhost | | 9fd9b8a4af3941f7aaa8d4ee1876d409 | nova | True | nova@localhost | | d4817354f0474935bbc5b4e6ca5a5862 | glance | True | glance@localhost | | de5640ce59c84367b78bfd97cf07eb6d | admin | True | test | | fe51e484199e43b7b452df12035e1730 | ykaul | True | ykaul | +----------------------------------+--------+---------+------------------+
I accidentaly reproduced this with old puddle: [folsom-rhel6.xxx] out: No handlers could be found for logger "keystoneclient.v2_0.client" [folsom-rhel6.xxx] out: Authorization Failed: Unable to communicate with identity service: Unable to find the server at external_server_value. (HTTP 400) It happens when OS_AUTH_URL is wrong: cat keystonerc_admin_bad export OS_USERNAME=admin export OS_TENANT_NAME=admin export OS_PASSWORD=verybadpass export OS_AUTH_URL=http://EXTERNAL_SERVER_VALUE:35357/v2.0/ export PS1="[\u@\h \W(keystone_admin)]$ " and trying something like keystone tenant-create --name=demo
[root@folsom-rhel6 ~(keystone_admin_bad)]$ keystone tenant-create --name=testik Authorization Failed: Unable to communicate with identity service: Unable to find the server at asdf. (HTTP 400) I think it has been fixed already.