Bug 2168092

Summary: Valid error message should be display on page if expected entry not found in Administer -> Settings Search box
Product: Red Hat Satellite Reporter: visawant
Component: SettingsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Shweta Singh <shwsingh>
Severity: medium Docs Contact:
Priority: high    
Version: 6.13.0CC: bbuckingham, lstejska, nalfassi, rlavi, shwsingh
Target Milestone: streamKeywords: MigratedToJIRA, Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:06:27 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 visawant 2023-02-08 07:48:04 UTC
Created attachment 1942822 [details]
Searching with Random input, no proper error message

Description of problem: Error message is not displaying on page after searching for any random entry inside search box. 


Version-Release number of selected component (if applicable): 6.13.0


How reproducible: Always


Steps to Reproduce:
1. Go to Administer -> Settings page
2. Inside search box, give any random input string which is not available
3. Click on search icon.

Actual results:
No error message displaying after search.


Expected results:
Proper error message should display. 
Error message ex- 'Not match found', 'No entries found', etc.

Additional info:
Attached screenshot.

Comment 1 Brad Buckingham 2023-02-16 15:36:57 UTC
Is this a regression from 6.12?  Thanks!

Comment 3 Marek Hulan 2023-02-16 16:11:18 UTC
I see the same behavior with 6.11 too.

Comment 4 visawant 2023-02-17 06:08:40 UTC
@bbuckingham NO it's not a regression
I can see the same behavior with 6.12

Comment 5 Girija Soni 2023-08-28 12:05:35 UTC
Created redmine issue https://projects.theforeman.org/issues/36705 from this bug

Comment 6 Bryan Kearney 2023-10-09 12:02:20 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36705 has been resolved.

Comment 8 Eric Helms 2024-06-06 16:06:27 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.