Incompatible version response
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Brant Knudson |
Bug Description
The XML response for the versions request (GET /) changed in Grizzly so that clients that worked with Folsom don't work with Grizzly.
Specifically, the link to the "stable" endpoint in Folsom is in the versions/
The Keystone server's response to a versions request on Grizzly should be compatible with the response in Folsom so that a client that worked with Folsom will work with Grizzly.
One way to fix this is to also include the link elements directly under the version elements. This way clients that are used to the current behavior will continue to work and clients that worked with Folsom will now work.
To recreate, use devstack. 'curl -H "Accept: application/xml" http://
BTW - I tried with application/json media-type and the response looks compatible, so it's just XML that's affected.
Here's the results from my system:
Folsom:
$ curl -H "Accept: application/xml" http://
<?xml version="1.0" encoding="UTF-8"?>
<versions xmlns="http://
<version status="stable" updated=
<media-types>
<media-type base="applicati
<media-type base="applicati
</media-types>
<link href="http://
<link href="http://
<link href="http://
</version>
</versions>
Grizzly:
$ curl -H "Accept: application/xml" http://
<?xml version="1.0" encoding="UTF-8"?>
<versions xmlns="http://
<version status="stable" updated=
<media-types>
<media-type base="applicati
<media-type base="applicati
</media-types>
<links>
<link href="http://
</links>
</version>
<version status="stable" updated=
<media-types>
<media-type base="applicati
<media-type base="applicati
</media-types>
<links>
<link href="http://
<link href="http://
<link href="http://
</links>
</version>
</versions>
Changed in keystone: | |
assignee: | nobody → Brant Knudson (blk-u) |
Changed in keystone: | |
milestone: | none → havana-2 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | havana-2 → 2013.2 |
I'm betting this is due to a xml middleware change in support of v3 API links?