domain-scoped token has "None" for tenant_id replacement
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Dave Chen |
Bug Description
When I get a domain-scoped token, I get back a catalog. The catalog contains a bunch of endpoints that aren't valid because the tenant_id replacement has been changed to "None" rather than a valid tenant-id.
Here's an example of the data in the auth request:
{
"token": {
"catalog": [
{
],
},
...
}
The compute endpoint in Keystone is like this:
| 677bffa798da42c
So it's replacing "$(tenant_id)s" with "None"
I don't think this is working as designed. What's the point of providing a bunch of invalid endpoints?
Changed in keystone: | |
assignee: | nobody → Dave Chen (wei-d-chen) |
Changed in keystone: | |
milestone: | none → kilo-3 |
Changed in keystone: | |
milestone: | kilo-3 → kilo-rc1 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | kilo-rc1 → 2015.1.0 |
Ideally we wouldn't have client-specific endpoints in the catalog at all, and drop support for this behavior entirely. However, in the short term... maybe just skip endpoints that expect to be string formatted with information that's not available?