Pagination not working in Kilo
Bug #1480787 reported by
Nayana
This bug report is a duplicate of:
Bug #1451402: v3 - pagination in GET services does not work.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I have created more than 100 users, but while I execute following command
GET http://<url>:35357/
I am getting list of all users.
I found this bug https:/
Can anyone confirm if pagination is supported in Identity API v3 or do I need to configure anything, so that pagination works?
Revision history for this message
| Dolph Mathews (dolph) wrote | #1 |
Revision history for this message
| Dolph Mathews (dolph) wrote | #2 |
Revision history for this message
| Dolph Mathews (dolph) wrote | #3 |
To post a comment you must log in.
Pagination has not been implemented. To do so, it must be entirely controlled by the server (not the API client) due to the requirement to support multiple backends (SQL vs LDAP, for example). The page & per_page scheme will not work for all drivers, and thus cannot be controlled by the end user, and is thus not a documented API. v3 does provide "next" and "previous" links for pagination purposes, but they are not currently populated. The closest behavior we have right now is server-defined limits on the number of resources returned by the backend in a single collection, which is controlled by keystone.conf list_limit.
I've marked this bug as a dupe of 1451402 and re-opened that bug against openstack-api-site. It must have slipped my bug radar in the leadup to the summit; my apologies!