GET details REST API next link missing 'details'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Steven Kaufer | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned | ||
OpenStack Compute (nova) |
Fix Released
|
High
|
Steven Kaufer |
Bug Description
When executing a pagination query a "next" link is included in the API reply when there are more items then the specified limit.
See pagination documentation for more information: http://
The caller should be able to invoke the "next" link (without having to re-format it) in order to get the next page of data. The documentation states "Subsequent links will honor the initial page size. Thus, a client may follow links to traverse a paginated collection without having to input the marker parameter."
The problem is that the "next" link is always scoped to the non-detailed query. For example, if you execute "/v2/<tenant>
This bug is caused because the "next" link is always generated by the _collection_name value in the ViewBuilder -- this name is always "servers".
Changed in nova: | |
assignee: | nobody → Steven Kaufer (kaufer) |
Changed in cinder: | |
assignee: | nobody → Steven Kaufer (kaufer) |
Changed in cinder: | |
importance: | Undecided → High |
tags: | added: icehouse-backport-potential |
Changed in nova: | |
importance: | Undecided → High |
Changed in cinder: | |
milestone: | none → juno-1 |
Changed in nova: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
status: | Fix Committed → Fix Released |
tags: | removed: icehouse-backport-potential |
Changed in nova: | |
milestone: | juno-1 → 2014.2 |
Changed in cinder: | |
milestone: | juno-1 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/84237
Review: https:/