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:
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:
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
> 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
+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
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.
https://access.redhat.com/errata/RHBA-2016:1500