Description of problem: We were trying to filter user/user groups/capsules/compute profiles/ compute resources. In filter, when we added field which was not present in list( any_string=any_string), it returned an error "Something went wrong" and log file had 500 Internal Server Error. Version-Release number of selected component (if applicable): satellite 6.3.0 snap 6.0 How reproducible: always Steps to Reproduce: 1. Navigate to Administer-> user/user groups/capsules/compute profiles/compute resources ( producible at any) 2. Filter as any_string=any_string Actual results: Shows the error as "Something went wrong" and the log file /var/log/foreman/production.log shows Rendered common/500.html.erb within layouts/application (3.7ms) 2017-07-10 09:32:35 7d7c37e3 [app] [I] Rendered layouts/_application_content.html.erb (0.5ms) 2017-07-10 09:32:35 7d7c37e3 [app] [I] Rendered layouts/base.html.erb (2.6ms) 2017-07-10 09:32:35 7d7c37e3 [app] [I] Completed 500 Internal Server Error Expected results: Error should be handled showing alert as "Field not recognised for searching" as happens in filtering hosts(Host -> All Hosts - > Filter ). Additional info:
Created attachment 1295840 [details] screenshot of UI
could you please attach the entire section of production log, starting with the GET request until the 500 error, with debug enabled? I could not reproduce this upstream.
Created attachment 1296144 [details] log in production.log file
Created redmine issue http://projects.theforeman.org/issues/20272 from this bug
Upstream bug assigned to tbrisker
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20272 has been resolved.
VERIFIED Version Tested: Satellite-6.3 Snap 11 Error is properly handled showing notification alert as "Invalid search query :Field not recognised for searching" while filtering user/user groups/capsules/compute profiles/compute resources with invalid search.
Created attachment 1312950 [details] screenshot of UI
Created attachment 1312951 [details] log in production.log file
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/RHSA-2018:0336