Grizzly v2 catalog has slight formatting changes compared to Folsom
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Dolph Mathews |
Bug Description
Although the contents are semantically the same, there are some slight changes between getting a catalog with Folsom and via the v2 api on Grizzly. I know of one deployment that broke becuase of this. Not sure if we need to fix this or not, but thought I should at least log this issue.
Here are two examples of tokens containing cat logs (changes indicated by [>>>>>This is New]):
Grizzly returns:
<token issued_
<tenant id="64794b84abf
<
</tenant>
</token>
<service type="compute" name="nova">
<
<endpoints> [>>>>>This is New]
<endpoint adminURL="http://
</endpoints> [>>>>>This is New]
</service>
Folsom returns:
<token expires=
<tenant id="62967bab438
<
</tenant>
</token>
<service type="compute" name="nova">
<endpoint adminURL="http://
</service>
summary: |
- Grizzly v2 catalog has slight formatting changes from Folsom + Grizzly v2 catalog has slight formatting changes compared to Folsom |
description: | updated |
description: | updated |
Changed in keystone: | |
importance: | Undecided → High |
Changed in keystone: | |
milestone: | grizzly-rc2 → 2013.1 |
This was recently fixed to match spec; need to assess impact & either revert or return two formats