Listing flavors with marker set returns 400

I am able to get the list the flavors after marker (up to limit) using the curl command as below.

REQ:

 curl -D - -H "X-Auth-Token: testuser:admin" -H "Accept: application/json" http://<ipaddress>:8774/v1.1/admin/flavors/detail?limit=1&marker=2

Response:
{"flavors": [{"vcpus": 2, "disk": 10, "name": "m1.medium", "links": [{"href": "http://<ipaddress>:8774/v1.1/admin/flavors/3", "rel": "self"}, {"href": "http://<ipaddress>:8774/admin/flavors/3", "rel": "bookmark"}], "rxtx_factor": 1.0, "OS-FLV-EXT-DATA:ephemeral": 40, "ram": 4096, "id": "3", "swap": ""}], "flavors_links": [{"href": "http://<ipaddress>:8774/v1.1/admin/flavors?limit=1&marker=3", "rel": "next"}]}

Kindly, Please elaborate on this..

I did some checking into this and found that it was still an issue. The problem is that limited_by_marker in api.openstack.common was checking for an 'id' key and flavors returned a 'flavorid' key.

Fix proposed to branch: master
Review: https://review.openstack.org/5693

Reviewed: https://review.openstack.org/5693
Committed: http://github.com/openstack/nova/commit/497502cbf833d063c964975448dfacd0e1db2ef4
Submitter: Jenkins
Branch: master

commit 497502cbf833d063c964975448dfacd0e1db2ef4
Author: Phlip Knouff <email address hidden>
Date: Mon Mar 26 22:16:27 2012 +0000

    Fix marker behavior for flavors

    Fixes Bug #956096

    Change-Id: Ifa94a70f2aec3b9527c291e27d4710336a1d1834

Fix proposed to branch: stable/essex
Review: https://review.openstack.org/9709

Reviewed: https://review.openstack.org/9709
Committed: http://github.com/openstack/nova/commit/d3a87a247e1c4a9dc9aa7b432d23b9c3c27d469a
Submitter: Jenkins
Branch: stable/essex

commit d3a87a247e1c4a9dc9aa7b432d23b9c3c27d469a
Author: Phlip Knouff <email address hidden>
Date: Mon Mar 26 22:16:27 2012 +0000

    Fix marker behavior for flavors

    Fixes Bug #956096

    (cherry-picked from commit 497502cbf833d063c964975448dfacd0e1db2ef4)

    Change-Id: I700770b17d0a38f120fce002167c8b6a8bbecbb2

Please find the attached test log from the Ubuntu Server Team's CI infrastructure. As part of the verification process for this bug, Nova has been deployed and configured across multiple nodes using precise-proposed as an installation source. After successful bring-up and configuration of the cluster, a number of exercises and smoke tests have be invoked to ensure the updated package did not introduce any regressions. A number of test iterations were carried out to catch any possible transient errors.

Please Note the list of installed packages at the top and bottom of the report.

For records of upstream test coverage of this update, please see the Jenkins links in the comments of the relevant upstream code-review(s):

Trunk review: https://review.openstack.org/5693
Stable review: https://review.openstack.org/9709

As per the provisional Micro Release Exception granted to this package by the Technical Board, we hope this contributes toward verification of this update.

Test coverage log.

This bug was fixed in the package nova - 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1

---------------
nova (2012.1.3+stable-20120827-4d2a4afe-0ubuntu1) precise-proposed; urgency=low

  * New upstream snapshot, fixes FTBFS in -proposed. (LP: #1041120)
  * Resynchronize with stable/essex (4d2a4afe):
    - [5d63601] Inappropriate exception handling on kvm live/block migration
      (LP: #917615)
    - [ae280ca] Deleted floating ips can cause instance delete to fail
      (LP: #1038266)

nova (2012.1.3+stable-20120824-86fb7362-0ubuntu1) precise-proposed; urgency=low

  * New upstream snapshot. (LP: #1041120)
  * Dropped, superseded by new snapshot:
    - debian/patches/CVE-2012-3447.patch: [d9577ce]
    - debian/patches/CVE-2012-3371.patch: [25f5bd3]
    - debian/patches/CVE-2012-3360+3361.patch: [b0feaff]
  * Resynchronize with stable/essex (86fb7362):
    - [86fb736] Libvirt driver reports incorrect error when volume-detach fails
      (LP: #1029463)
    - [272b98d] nova delete lxc-instance umounts the wrong rootfs (LP: #971621)
    - [09217ab] Block storage connections are NOT restored on system reboot
      (LP: #1036902)
    - [d9577ce] CVE-2012-3361 not fully addressed (LP: #1031311)
    - [e8ef050] pycrypto is unused and the existing code is potentially insecure
      to use (LP: #1033178)
    - [3b4ac31] cannot umount guestfs (LP: #1013689)
    - [f8255f3] qpid_heartbeat setting in ineffective (LP: #1030430)
    - [413c641] Deallocation of fixed IP occurs before security group refresh
      leading to potential security issue in error / race conditions
      (LP: #1021352)
    - [219c5ca] Race condition in network/deallocate_for_instance() leads to
      security issue (LP: #1021340)
    - [f2bc403] cleanup_file_locks does not remove stale sentinel files
      (LP: #1018586)
    - [4c7d671] Deleting Flavor currently in use by instance creates error
      (LP: #994935)
    - [7e88e39] nova testsuite errors on newer versions of python-boto (e.g.
      2.5.2) (LP: #1027984)
    - [80d3026] NoMoreFloatingIps: Zero floating ips available after repeatedly
      creating and destroying instances over time (LP: #1017418)
    - [4d74631] Launching with source groups under load produces lazy load error
      (LP: #1018721)
    - [08e5128] API 'v1.1/{tenant_id}/os-hosts' does not return a list of hosts
      (LP: #1014925)
    - [801b94a] Restarting nova-compute removes ip packet filters (LP: #1027105)
    - [f6d1f55] instance live migration should create virtual_size disk image
      (LP: #977007)
    - [4b89b4f] [nova][volumes] Exceeding volumes, gigabytes and floating_ips
      quotas returns general uninformative HTTP 500 error (LP: #1021373)
    - [6e873bc] [nova][volumes] Exceeding volumes, gigabytes and floating_ips
      quotas returns general uninformative HTTP 500 error (LP: #1021373)
    - [7b215ed] Use default qemu-img cluster size in libvirt connection driver
    - [d3a87a2] Listing flavors with marker set returns 400 (LP: #956096)
    - [cf6a85a] nova-rootwrap hardcodes paths instead of using
      /sbin:/usr/sbin:/usr/bin:/bin (LP: #1013147)
    - [2efc87c] affinity filters don't work if scheduler_hints is None
      (LP: #1007573)
  ...

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.