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.
displayMessage:"Field 'foo' not recognized for searching!"
0:"Field 'foo' not recognized for searching!"
Version-Release number of selected component (if applicable):
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)
the error is not being handled by UI, renders the form unusable.
Notification is shown or some default behavior takes place.
Created redmine issue http://projects.theforeman.org/issues/12140 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/12140 has been closed
Moving this back to NEW as the issue status was changed back (it is still a bug upstream) http://projects.theforeman.org/issues/12140
This was fixed upstream https://github.com/Katello/katello/pull/5819
Ok, this is working pretty nice now, but it still generates the empty suggestion instead showing the error in the suggestion box just like Foreman does.
I'm putting this to FAILEDQA. If you think this should be reported as a standalone bug, let me know and I'll put this one to VERIFIED
(In reply to Roman Plevka from comment #6)
> Ok, this is working pretty nice now, but it still generates the empty
> suggestion instead showing the error in the suggestion box just like Foreman
> I'm putting this to FAILEDQA. If you think this should be reported as a
> standalone bug, let me know and I'll put this one to VERIFIED
+1 to a standalone bug for the empty suggestion box, I actually have opened up an upstream bug here for this issue and can clone it to BZ. http://projects.theforeman.org/issues/13118
putting this bug to verified as the other issue now has its own BZ #1322088
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.