Bug 1688369

Description of problem:

Summary says it all, particular example  -see reproducer.


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


How reproducible:
100%


Steps to Reproduce:
1. Have many errata that apply to some filter in a CV
2. Find the CV filter ID - it will be 1st column in output:
su - postgres -c "psql foreman -c \"select * from katello_content_view_filters;\""

3. Having the filter id stored in bash variable ID, run the query:

curl -X GET -s -k -u admin:verysecretpassword "https://$(hostname -f)/katello/api/v2/errata?available_for=content_view_filter&filterId=${ID}&full_result=true&page=1&paged=true&per_page=30&search=&sort_by=issued&sort_order=DESC" > errata_available_for_${ID}.json

4. Check real pagination settings of the query:

cat errata_available_for_${ID}.json | python -m json.tool | grep "[\"_]page\""


Actual results:
Regardless what pagination one sets in "per_page" (or I guess also in "page") in the URI request, the output will have:

    "page": "1",
    "per_page": 9496,

(where the per_page value will match exactly the number of errata returned - "grep -c errata_id" will return the same)



Expected results:
page and per_page is applied properly


Additional info:
The query itself is quite imperformant - long postgres SELECT taking much CPU is run for a loong time (12min on a customer DB on idle Satellite). Not sure if worth improving that as well..?