blazar host-list with identity_uri set

CLIENT console:
[root@k-cloud ~(blazar_blazar)]#
[root@k-cloud ~(blazar_blazar)]# blazar host-list
Starting new HTTP connection (1): 10.20.0.20
Resetting dropped connection: 10.20.0.20
Starting new HTTP connection (1): 10.20.0.20
ERROR: {u'message': u'The server is currently unavailable. Please try again at a later time.<br /><br />\n\n\n', u'code': u'503 Service Unavailable', u'title': u'Service Unavailable'}
[root@k-cloud ~(blazar_blazar)]#



blazar-manager/api console stdoutput errors:
[root@k-cloud ~(keystone_admin)]# (14299) accepted ('10.20.0.20', 43482)
2017-06-07 14:13:18.560 14299 WARNING keystonemiddleware.auth_token [-] Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use  memcache for the auth_token token cache by setting the memcached_servers option.
2017-06-07 14:13:18.572 14299 ERROR keystonemiddleware.auth_token [-] Bad response code while validating token: 400
2017-06-07 14:13:18.579 14299 WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "Expecting to find username or userId in passwordCredentials. The server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error.", "code": 400, "title": "Bad Request"}}
2017-06-07 14:13:18.579 14299 CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Failed to fetch token data from identity server
10.20.0.20 - - [07/Jun/2017 14:13:18] "GET /v1/os-hosts HTTP/1.1" 503 335 0.020658