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 1498827

Summary: UI/Content Hosts page remembers first search and prevents any further searches
Product: Red Hat Satellite Reporter: Stanislav Tkachenko <stkachen>
Component: Hosts - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bbuckingham, sjagtap, stkachen
Target Milestone: UnspecifiedKeywords: Regression
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-10-19 12:23:29 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 Stanislav Tkachenko 2017-10-05 10:57:11 UTC
Description of problem:
After the first search Content Hosts page remembers first search criteria and will use it despite any further criteria changes.

Example:
1. Navigate to Content Hosts page. URL is
https://sat6.com/content_hosts?page=1&per_page=20&sortBy=name&sortOrder=ASC
2. Hit any search, e.g. 'name = x'. Hosts filtered by name, URL is
https://sat6.com/content_hosts?page=1&per_page=20&sortBy=name&sortOrder=ASC&search=name%20%3D%20x
3. Hit another search, e.g. 'subscription_status = valid'. At first it will try to filter by subscription status but then page will be immediately reloaded and filtered by name. URL is
https://sat6.com/content_hosts?page=1&per_page=20&sortBy=name&sortOrder=ASC&search=name%20%3D%20x

Page reload does not help, you need  to navigate to any other page then back to the Content Hosts page to perform another search.

Version-Release number of selected component (if applicable):
Satellite 6.3.0-18:
* satellite-6.3.0-19.0.beta.el7sat.noarch
* katello-3.4.5-3.el7sat.noarch
* foreman-1.15.4.3-1.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:
1. (Optional) Register content host
2. Navigate to Content Hosts page
3. Perform any valid search, check URL and that host is displayed.
4. Perform any non-valid search, check URL, search field and that host still is displayed.

Actual results:
First search criteria is remembered and any further searches have no effect.

Expected results:
Search criteria be updated when it is changed.

Additional info:

Comment 3 Brad Buckingham 2017-10-13 14:36:47 UTC
Is this a duplicate of bug 1495271?

Comment 4 Stanislav Tkachenko 2017-10-19 09:46:00 UTC
(In reply to Brad Buckingham from comment #3)
> Is this a duplicate of bug 1495271?

Yes, indeed, I've missed that while filling this bug.

Comment 5 Brad Buckingham 2017-10-19 12:23:29 UTC

*** This bug has been marked as a duplicate of bug 1495271 ***