A cached schema breaks 'fall back to v1' logic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance Client |
Fix Released
|
Medium
|
Flavio Percoco |
Bug Description
Fallback to v1 doesn't work if the schema has been cached previously.
Pointing a client at a v1 only server, when no api version has been specified, should result in falling back to a v1 call.
If the schema has been cached this doesn't happen:
$ glance --os-tenant-
HTTPMultipleChoices (HTTP 300) Requested version of OpenStack Images API is not available.
Removing the schema from ~/.glanceclient gives the expected behaviour:
$ glance --os-tenant-
WARNING: The client is falling back to v1 because the accessing to v2 failed. This behavior will be removed in future versions
+------
| Property | Value |
+------
| checksum | a16a81de3d944eb
| container_format | bare |
| created_at | 2014-07-31T12:48:53 |
| deleted | False |
| disk_format | raw |
| id | d6bc96f0-
| is_public | False |
| min_disk | 0 |
| min_ram | 0 |
| name | x |
| owner | 61624292678963 |
| protected | False |
| size | 1048576000 |
| status | active |
| updated_at | 2014-07-31T12:49:47 |
+------
tags: | added: 1.0.0-potential |
Changed in python-glanceclient: | |
milestone: | none → 1.1.0 |
status: | Fix Committed → Fix Released |
https:/ /review. openstack. org/#/c/ 219469/