Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1642549

Summary: Content Host filter is showing only 1 page of result
Product: Red Hat Satellite Reporter: Anand Agrawal <aagrawal>
Component: Hosts - ContentAssignee: John Mitsch <jomitsch>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4CC: akarimi, alexander.lackner, christoph.roeder, felician.moldovan, gpadholi, jsenkyri, millard.matt, mkalyat, mmccune, nsamant, pcreech, shisingh, slutade, swadeley, swick
Target Milestone: 6.5.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1661293 (view as bug list) Environment:
Last Closed: 2019-05-14 12:38:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Anand Agrawal 2018-10-24 16:09:22 UTC
Description of problem:
When applying a filter on the content host page we only get one page of results back, for example, if we filter for "os_major = 7" we only get 20 results which is exactly one page (per-page). We have way over 40 RHEL 7 content hosts registered to our Satellite Server.


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

How reproducible:
Always

Steps to Reproduce:
1. Hosts -> Content Hosts
2. Filter os_major = 7
3. This will show the result only up to the per_page setting, next page option not available

Actual results:
It doesn't show page 2 or more records

Expected results:
It should show more pages if the filter is applicable.

Additional info:

Comment 2 Samson Wick 2018-11-06 20:38:23 UTC
I'm having the exact problem described here at a different customer, but wanted to add the detail that by altering "per_page" value in the URL to a very large number (example 500), the UI maximum of 100/page can be exceeded and all results will show up on the 1 page of filtered results.  Further, this larger per_page value will continue to be used by the UI for subsequent searches.

Example:

https://satellite.example.com/content_hosts?page=1&per_page=500&sortBy=name&sortOrder=ASC&search=%20hypervisor%20%3D%20%20false

Comment 3 Matt Millard 2018-11-09 14:46:30 UTC
I'll also add that by changing the page= to a larger number that page will show up even if it says there are only 1 page.  For page 5 you would just set page=5.

Comment 5 John Mitsch 2018-12-06 14:04:38 UTC
Connecting redmine issue https://projects.theforeman.org/issues/25487 from this bug

Comment 7 Brad Buckingham 2018-12-07 13:25:48 UTC
*** Bug 1652489 has been marked as a duplicate of this bug. ***

Comment 11 errata-xmlrpc 2019-05-14 12:38:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:1222

Comment 12 Brad Buckingham 2019-09-23 18:11:33 UTC
*** Bug 1704865 has been marked as a duplicate of this bug. ***