API v3 users.list limits result
Bug #1079661 reported by
Andre Naehring
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Undecided
|
Dolph Mathews |
Bug Description
experimenting with v3:
---
from keystoneclient.v3 import client
kc = client.
users = kc.users.list()
print users
---
The result is limited to (if I count correct) 30 users. Using the same with v2 of the API and client, I receive the whole list of a thousand users (test database). All users are assigned to the same tenant, the query is not limited to one project / tenant. I receive users of different tenants, but only 30 with v3.
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | grizzly-3 → 2013.1 |
Changed in python-keystoneclient: | |
assignee: | nobody → 牛振国 (niu-zglinux) |
Changed in python-keystoneclient: | |
assignee: | 牛振国 (niu-zglinux) → nobody |
no longer affects: | python-keystoneclient |
To post a comment you must log in.
Moved this bug to keystone because it's the controllers that are defaulting to 30 results per page, but we haven't actually exposed paging to the API yet. Either the default paging needs to be removed, or the API implementation and client need to be updated to support paging.
This is spec'd in identity-api v3 for all collections as:
"links": {
"previous": url,
"self": url,
"next": url,
}
Where next/previous could be null if you're at either limit of the pagination.