Bug #12140: scoped_search - err 500 on searching on invalid field - Katello - Foreman

Actions

Copy link

Bug #12140

closed

scoped_search - err 500 on searching on invalid field

Added by roman plevka over 9 years ago. Updated almost 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

John Mitsch

Category:

Web UI

Target version:

Katello 3.0.0

Difficulty:

Triaged:

Bugzilla link:

1270855

Pull request:

https://github.com/Katello/katello/pull/5819, https://github.com/Katello/bastion/pull/97

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1270855
Description of problem:
Applies to all katello entities:
on sending a query which uses a non-existing field, server returns error 500, but the GUI does not handle this error.
This results in 'dead' search form.

Request url:
https://<fqdn>/katello/api/v2/content_views?nondefault=true&organization_id=3&page=1&search=foo+%3D+bar&sort_by=name&sort_order=ASC

Response:
displayMessage:"Field 'foo' not recognized for searching!"
errors:Array:
0:"Field 'foo' not recognized for searching!"

Version-Release number of selected component (if applicable):
katello-2.4.0-6.nightly.el7.noarch
tfm-rubygem-scoped_search-3.2.2-2.el7.noarch

How reproducible:
every time on all katello entities

Steps to Reproduce:
1. go to a katello entity page (e.g. Content Views)
2. input the seaerch query with invalid field name - e.g. foo = bar
3. Hit search
4. No response on GUI (Error in the captured repsonse headers)

Actual results:
the error is not being handled by UI, renders the form unusable.

Expected results:
Notification is shown or some default behavior takes place.

Additional info: