Activity log for bug #1001345

Date Who What changed Old value New value Message
2012-05-18 16:51:06 clayg bug added bug
2012-05-21 18:01:02 Brian Waldon description Is this the right project for python-novaclient "bugs"? 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-snapshot-show <display_name>" you'll get an error: $nova volume-snapshot-show <display_name> ERROR: No snapshot with a name or ID of '<display_name>' exists. Where as a "nova volume-snapshot-show <uuid>" will just make the GET directly on the resource, and of course works as expected. 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? 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-snapshot-show <display_name>" you'll get an error:     $nova volume-snapshot-show <display_name>     ERROR: No snapshot with a name or ID of '<display_name>' exists. Where as a "nova volume-snapshot-show <uuid>" will just make the GET directly on the resource, and of course works as expected. 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?
2012-05-21 18:04:19 Brian Waldon nova: status New Triaged
2012-05-21 18:04:24 Brian Waldon nova: importance Undecided Low
2012-07-04 10:38:47 Thierry Carrez affects nova python-novaclient
2013-01-02 20:11:32 Anita Kuno python-novaclient: assignee Anita Kuno (akuno)
2013-02-18 20:15:00 OpenStack Infra python-novaclient: status Triaged In Progress
2013-03-01 23:01:17 OpenStack Infra python-novaclient: status In Progress Fix Committed
2013-08-06 14:38:43 Russell Bryant python-novaclient: status Fix Committed Fix Released