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.

Description of problem:
"Filter by Status:" is not working if the user tried to use pagination 

Version-Release number of selected component (if applicable):
Satellite 6.5 Snap 6

How reproducible:
Always 

Steps to Reproduce:
1.Navigate to https://<Sathost>/content_hosts/4/module-streams?page=3&per_page=20
2.Install module stream in client host (e.g. dnf module install php)
3.On Content Host-> Module Stream Page-> Use Pagiantion e.g. naviagate to last page
4.try to use filter "Filter by Status:"

Actual results:
The Filter is not working after use of pagination 

Expected results:
The Filter should work in all cases instead of on pagination 

Additional info:

Created redmine issue https://projects.theforeman.org/issues/25627 from 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