Bug 1038273

Description of problem:

When calling /owners/<key>/pools with paging the expected results are not returned beyond the first page. Instead, we get an empty page.

The following output was generated by API calls in RHSM Web:

all available,matching pools for a consumer (no paging)
Fetching pools: /owners/5394945/pools?consumer=0cb583db-d949-4316-a37f-adbab3ff2132&listall=false&
Got pools: 19

Using paging: first page, ten per:
Fetching pools: /owners/5394945/pools?consumer=0cb583db-d949-4316-a37f-adbab3ff2132&listall=false&page=1&per_page=10&
Got pools: 10


The above is well and fine. Then we look at the link headers we get back:
Server: Apache-Coyote/1.1
X-Candlepin-Version: 0.8.28.1-1
Link: <https://subscription.rhn.qa.redhat.com/subscription/consumers//owners/5394945/pools?per_page=10&listall=false&consumer=0cb583db-d949-4316-a37f-adbab3ff2132&page=1>; rel="first", <https://subscription.rhn.qa.redhat.com/subscription/consumers//owners/5394945/pools?per_page=10&listall=false&consumer=0cb583db-d949-4316-a37f-adbab3ff2132&page=1>; rel="last"
Content-Type: application/json
Transfer-Encoding: chunked
Date: Tue, 03 Dec 2013 21:19:43 GMT

Notice

1) It says the last page is page 1. There are 9 results not returned on the first page as queried. They should be on page 2 which would also be the last page

2) The URL given back is not correct: /consumers//owners
It'd be nice if we were given a [correct] URL which began at /owners and did not include the whole hostname since we do not talk to subscription.rhn.redhat.com within rhsm-web.

3) Querying directly for page 2, one would expect to get the remaining 9 pools back, but it is an empty page.


Version-Release number of selected component (if applicable): 0.8.28


How reproducible: Always


Steps to Reproduce:
1. Configure a consumer to have some available pools
2. Call candlpin /owners/<key>/pools API with paging such that per_page is < the total available bools

Actual results:
Beyond the first page the data is not returned correctly -> the pages are empty. The link headers are also incorrect.

Expected results:
pages > 1 should have the correct (non-empty) data if it exists. Link headers should be accurate.


Additional info: We plan to enable paging for pools, entitlements, and consumers in RHSM web. Please review these other APIS to ensure they do not have these same issues.