novaclient support for offset
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-novaclient |
Fix Released
|
Low
|
Anita Kuno |
Bug Description
The novaclient does not appear to support (or I don't know how to use) the offset parameter when doing listings. This seems to effect most/all collections. (e.g. instances, volumes, and most notably volume-snapshots, of which there can be "lots-ish".)
Either way, when your result set exceeds the default api limit (1000?) you get some surprising behavior. If you ask for "nova volume-
$nova volume-
ERROR: No snapshot with a name or ID of '<display_name>' exists.
Where as a "nova volume-
Unfortunately, I can't figure out how to get the uuid of the volume without dropping down to curl and doing offset queries.
Seems like the client could automatically make extra request(s) if the result set is exactly the same length as a negotiated/default "limit" and may have been truncated? Or at least support offset as a command like option?
affects: | nova → python-novaclient |
Changed in python-novaclient: | |
assignee: | nobody → Anita Kuno (akuno) |
Changed in python-novaclient: | |
status: | Triaged → In Progress |
Changed in python-novaclient: | |
status: | Fix Committed → Fix Released |
Yes, this is where you file bugs on python-novaclient.