Confirmed that the issue doesn't seem to affect heat CLI.
While Congress is encountering authentication errors accessing heat, I could use the heat CLI to access heat information without issue. (e.g., $ heat config-list).
Also, here are the corresponding logs between Congress showing error authenticating and h-api showing failed authentication token.
Confirmed that the issue doesn't seem to affect heat CLI.
While Congress is encountering authentication errors accessing heat, I could use the heat CLI to access heat information without issue. (e.g., $ heat config-list).
Also, here are the corresponding logs between Congress showing error authenticating and h-api showing failed authentication token.
Congress: datasources. datasource_ driver [[00;36m-[01;31m] [01;35m [01;31mDatasour ce driver raised exception[00m datasources. datasource_ driver [01;35m [00mHTTPUnautho rized: ERROR: Authentication failed: Authentication required datasources. datasource_ driver [[00;36m-[01;31m] [01;35m [01;31mDatasour ce driver raised exception[00m datasources. datasource_ driver [01;35m [00mHTTPUnautho rized: ERROR: Authentication failed: Authentication required datasources. datasource_ driver [[00;36m-[01;31m] [01;35m [01;31mDatasour ce driver raised exception[00m datasources. datasource_ driver [01;35m [00mHTTPUnautho rized: ERROR: Authentication failed: Authentication required
2016-03-18 16:55:17.516 [01;31mERROR congress.
[01;31m2016-03-18 16:55:17.516 TRACE congress.
2016-03-18 16:55:27.546 [01;31mERROR congress.
[01;31m2016-03-18 16:55:27.546 TRACE congress.
2016-03-18 16:55:37.582 [01;31mERROR congress.
[01;31m2016-03-18 16:55:37.582 TRACE congress.
h-api: are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mAuthoriz ation failed for token[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mIdentity response: {"error": {"message": "Could not find token: a8a3a526ca5f49a 4b2572cc49a0f6c 2f", "code": 404, "title": "Not Found"}}[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mAuthoriz ation failed for token[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mAuthoriz ation failed for token[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mIdentity response: {"error": {"message": "Could not find token: a8a3a526ca5f49a 4b2572cc49a0f6c 2f", "code": 404, "title": "Not Found"}}[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mAuthoriz ation failed for token[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mAuthoriz ation failed for token[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mIdentity response: {"error": {"message": "Could not find token: a8a3a526ca5f49a 4b2572cc49a0f6c 2f", "code": 404, "title": "Not Found"}}[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mAuthoriz ation failed for token[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mAuthoriz ation failed for token[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mIdentity response: {"error": {"message": "Could not find token: a8a3a526ca5f49a 4b2572cc49a0f6c 2f", "code": 404, "title": "Not Found"}}[00m are.auth_ token [[00;36m-[01;33m] [01;35m [01;33mAuthoriz ation failed for token
2016-03-18 16:55:07.478 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:07.478 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:07.479 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:17.514 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:17.514 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:17.515 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:27.543 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:27.543 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:27.544 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:37.577 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:37.578 [01;33mWARNING keystonemiddlew
2016-03-18 16:55:37.578 [01;33mWARNING keystonemiddlew