cache management API is hardcoded under /v1
Bug #1135537 reported by
Eoghan Glynn
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Won't Fix
|
High
|
Flavio Percoco |
Bug Description
The cachemanagement API is hardcoded to use v1:
https:/
whereas if the v2 API is enabled, but not v1, this is problematic as clients would want to use v2 across the board.
Changed in glance: | |
assignee: | nobody → Flavio Percoco Premoli (flaper87) |
To post a comment you must log in.
With v1 disabled, this is what happens when you try to GET /v1/cached_images
$ curl -H "X-Auth-Token: $tok" http:// 10.130. 50.34:9292/ v1/cached_ images | python -m json.tool
Dload Upload Total Spent Left Speed
"links" : [
" href": "http:// 10.130. 50.34:9292/ v2/",
" rel": "self"
"status" : "CURRENT"
% Total % Received % Xferd Average Speed Time Time Time Current
100 119 100 119 0 0 25142 0 --:--:-- --:--:-- --:--:-- 29750
{
"versions": [
{
"id": "v2.0",
{
}
],
}
]
}