"image list" commands new --limit and --marker options have unintended side effects
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-openstackclient |
New
|
Undecided
|
Unassigned |
Bug Description
This Bugreport: https:/
But the problem here lies with the serversides api default limit of 25 and the order of application of the several command line options. While limit or marker are applied first along the api request, e.g. property or sortorder are applied on the received data in a second step.
see lines 460 - 508
https:/
So the list is already shortened before any filter or sorting is applied, missing images you were looking for.
This Problem didn't exist in the old code, because by default all images were fetched: https:/
My workaround for now is to set an extreme limit...
I guess, the serverside api doesn't allow filter and sorting. As long as this is the case, the code should be changed to ignore limit or marker if any clientside filter or sort is set. And this should be documented.