v3 - pagination in GET services does not work
Bug #1451402 reported by
Jamie Hannaford
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Undecided
|
Unassigned | ||
openstack-api-site |
Fix Released
|
High
|
Diane Fleming |
Bug Description
When I execute
GET http://
I expect to see a paginated collection returned (5 resources in total), however this is not the case. Instead I get back the full collection - so it seems like the query params are being ignored.
The next and prev links don't reference the next page in the collection either.
Do I need to configure the conf file or something? If so, I couldn't find it documented anywhere.
Changed in openstack-api-site: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in openstack-api-site: | |
assignee: | nobody → Atsushi SAKAI (sakaia) |
tags: | added: keystone |
Changed in keystone: | |
status: | Expired → Confirmed |
Changed in openstack-api-site: | |
assignee: | Atsushi SAKAI (sakaia) → Diane Fleming (diane-fleming) |
milestone: | none → liberty |
importance: | Medium → High |
tags: | removed: keystone |
To post a comment you must log in.
Where are page and per_page parameters documented with respect to v3? The next and previous links are intended to give the backend driver control over pagination. There's no guaranteed support for API users to make arbitrary pagination queries that are not provided by the backend due to the difference in pagination strategies required for different backends (SQL vs LDAP, for example).