Description of problem: It is possible to list all active entitlements for an owner with: GET /candlepin/owners/{ownerId}/entitlements However, if the list of entitlements is too great, it is also possible (or so I was informed) to attach the following query in order to paginate through the entitlements: ?page=1&per_page=2 However, what I'm seeing is that the page and per_page query parameters are ignored, and ALL of the entitlements are returned, no matter what. Version-Release number of selected component (if applicable): 0.9.51.x How reproducible: Always Steps to Reproduce: 1. Create (or find) an owner with at least two active entitlements. In stage, an owner fitting this constraint is 7624949. 2. Make a request to list entitlements, 1-per-page: curl -ku $CPADMIN_USER:$CPADMIN_PASS -X GET 'http://candlepindomain/candlepin/owners/7624949/entitlements?page=1&per_page=1' 3. Count the number of entitlements returned by the request. Actual results: All four entitlements for owner 7624949 were returned. Expected results: Only the first entitlement (by creation date) should have been returned. Additional info: It's easier to count the results if you use jq (sudo yum install jq): curl -ku $CPADMIN_USER:$CPADMIN_PASS -X GET 'http://candlepindomain/candlepin/owners/7624949/entitlements?page=1&per_page=1' | jq '. | length' - (returns "4")
This was fixed in Candlepin 2.0