commit b0e4cc1b63911710524005855aeefadc0850f44b
Author: Steven Kaufer <email address hidden>
Date: Mon Dec 15 22:52:18 2014 +0000
Client output is not sorted by --sort_key
The cinder client supports invoking the volumes REST API with the
sort_dir and sort_key parameters. However, the client output table
is always sorted by ID even though the REST API is returning in
sorted order based on the sort key/direction provided.
For example, the command below supplies the 'size' sort key but the
output table is still sorted by ID:
cinder list --sort_key size --sort_dir desc
This fix contains:
* Updates to the print_list utility to prevent any re-ordering so
that the current object order is maintained
* Updates to the shell to disable re-ordering if the user supplies
sort parameters
Reviewed: https:/ /review. openstack. org/141964 /git.openstack. org/cgit/ openstack/ python- cinderclient/ commit/ ?id=b0e4cc1b639 11710524005855a eefadc0850f44b
Committed: https:/
Submitter: Jenkins
Branch: master
commit b0e4cc1b6391171 0524005855aeefa dc0850f44b
Author: Steven Kaufer <email address hidden>
Date: Mon Dec 15 22:52:18 2014 +0000
Client output is not sorted by --sort_key
The cinder client supports invoking the volumes REST API with the
sort_dir and sort_key parameters. However, the client output table
is always sorted by ID even though the REST API is returning in
sorted order based on the sort key/direction provided.
For example, the command below supplies the 'size' sort key but the
output table is still sorted by ID:
cinder list --sort_key size --sort_dir desc
This fix contains:
* Updates to the print_list utility to prevent any re-ordering so
that the current object order is maintained
* Updates to the shell to disable re-ordering if the user supplies
sort parameters
Change-Id: I4cc111a8bdd2b8 9158dfc4bb0d16f a6dbf36cc57
Closes-Bug: 1402846