Bug 1729386 - searching for a nonexistent model causes "loading" indication (spinning wheel) to stay forever
Summary: searching for a nonexistent model causes "loading" indication (spinning wheel...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Search
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: tstrych
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-12 07:36 UTC by Jan Hutař
Modified: 2021-05-27 01:58 UTC (History)
7 users (show)

Fixed In Version: foreman-2.3.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-27 01:58:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
6.6 vs 6.5 on same reproducer (61.69 KB, image/png)
2019-07-12 07:45 UTC, Jan Hutař 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 31198 0 Normal Closed Search doesn't work on the models page 2021-04-01 12:09:21 UTC

Description Jan Hutař 2019-07-12 07:36:24 UTC 
Description of problem:
Searching for a nonexistent model causes "loading" indication (spinning wheel) to stay forever


Version-Release number of selected component (if applicable):
satellite-6.6.0-5.beta.el7sat.noarch (snap 10)


How reproducible:
always


Steps to Reproduce:
1. Hosts -> Hardware Models
2. Enter random string to the search bar (hw model name that does not exist)
3. Start the search


Actual results:
"No entries found" shown, but spinning wheel is still spinning. See screenshot.


Expected results:
No ongoing progress indication once search itself is done.
Comment 3 Jan Hutař 2019-07-12 07:45:21 UTC 
Created attachment 1589783 [details]
6.6 vs 6.5 on same reproducer
Comment 4 Ondřej Ezr 2021-04-01 12:09:24 UTC 
This has been resolved before Sat-6.9 rebase, so the fix is in 6.9 already.
Note You need to log in before you can comment on or make changes to this bug.