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.
Description of problem:
On the "Monitor" -> "Tasks" page, if the user searches for a word, and then clicks the "search" button a second time to update the results, it does nothing.
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.7.4
How reproducible:
Steps to Reproduce:
1. Produce an action that generates a task. (I ran a remote job against a host "myhostname"
2. Type "myhostname" in the search field and click the search button
3. Observe resulting task being found.
4. Without navigating away from that Tasks page, perform an action that will generate another task that should show for that search. (Example: In another browser window or via hammer, schedule another remote job against that same host).
5. Back in the Tasks window, without changing the search field, click the "Search" button again.
Actual results:
- The search results are not updated.
- Clicking the search button does NOT result in another GET in the /var/log/foreman/production.log log.
Expected results:
When clicking search with a valid search term, regardless of prior actions, it should search and display relevant results.
Additional info:
The following is observed during the first search in /var/log/foreman/production.log.
2020-12-15T14:49:13 [I|app|114ac7e1] Started GET "/foreman_tasks/api/tasks?search=myhostname&page=1&include_permissions=true" for 192.168.x.x at 2020-12-15 14:49:13 +0000
2020-12-15T14:49:13 [I|app|114ac7e1] Processing by ForemanTasks::Api::TasksController#index as JSON
2020-12-15T14:49:13 [I|app|114ac7e1] Parameters: {"search"=>"myhostname", "page"=>"1", "include_permissions"=>"true"}
However, there is no resulting log entry from a subsequent click of the search button, unless the search field is modified (add whitespace). The second task (from reproduction step 4) will also not show up in the results unless the search field is modified (not just clicked on), or the tasks page is entirely reloaded.
I'm not seeing any dedicated "Refresh data" button on the page (in 6.7.z), but I do see it in the v6.8 UI. I suspect it was added in the most recent version with the other task page changes.
However, Refreshing the page itself (via a browser page reload) is an acceptable workaround, as is modifying the search to add whitespace.
(The behaviour of not searching on the second click of the search button remains the same between versions though)
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 (Moderate: Satellite 6.9 Release), 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-2021:1313
Description of problem: On the "Monitor" -> "Tasks" page, if the user searches for a word, and then clicks the "search" button a second time to update the results, it does nothing. Version-Release number of selected component (if applicable): Red Hat Satellite 6.7.4 How reproducible: Steps to Reproduce: 1. Produce an action that generates a task. (I ran a remote job against a host "myhostname" 2. Type "myhostname" in the search field and click the search button 3. Observe resulting task being found. 4. Without navigating away from that Tasks page, perform an action that will generate another task that should show for that search. (Example: In another browser window or via hammer, schedule another remote job against that same host). 5. Back in the Tasks window, without changing the search field, click the "Search" button again. Actual results: - The search results are not updated. - Clicking the search button does NOT result in another GET in the /var/log/foreman/production.log log. Expected results: When clicking search with a valid search term, regardless of prior actions, it should search and display relevant results. Additional info: The following is observed during the first search in /var/log/foreman/production.log. 2020-12-15T14:49:13 [I|app|114ac7e1] Started GET "/foreman_tasks/api/tasks?search=myhostname&page=1&include_permissions=true" for 192.168.x.x at 2020-12-15 14:49:13 +0000 2020-12-15T14:49:13 [I|app|114ac7e1] Processing by ForemanTasks::Api::TasksController#index as JSON 2020-12-15T14:49:13 [I|app|114ac7e1] Parameters: {"search"=>"myhostname", "page"=>"1", "include_permissions"=>"true"} However, there is no resulting log entry from a subsequent click of the search button, unless the search field is modified (add whitespace). The second task (from reproduction step 4) will also not show up in the results unless the search field is modified (not just clicked on), or the tasks page is entirely reloaded.