Bug 1642549
Summary: | Content Host filter is showing only 1 page of result | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Anand Agrawal <aagrawal> | |
Component: | Hosts - Content | Assignee: | John Mitsch <jomitsch> | |
Status: | CLOSED ERRATA | QA Contact: | Stephen Wadeley <swadeley> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.4 | CC: | akarimi, alexander.lackner, christoph.roeder, felician.moldovan, gpadholi, jsenkyri, millard.matt, mkalyat, mmccune, nsamant, pcreech, shisingh, slutade, swadeley, swick | |
Target Milestone: | 6.5.0 | Keywords: | 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
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 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. Connecting redmine issue https://projects.theforeman.org/issues/25487 from this bug *** Bug 1652489 has been marked as a duplicate of this bug. *** 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 *** Bug 1704865 has been marked as a duplicate of this bug. *** |