Hide Forgot
Description of problem: compliance report searches fails when searching for reports related to compliance_failed, compliance_passed to name a few, there are isues with many other searches as well. 2016-03-31 22:21:58 [app] [I] Started GET "/compliance/arf_reports?utf8=%E2%9C%93&search=+compliance_failed+" for 10.10.52.71 at 2016-03-31 22:21:58 -0400 2016-03-31 22:21:58 [app] [I] Processing by ArfReportsController#index as HTML 2016-03-31 22:21:58 [app] [I] Parameters: {"utf8"=>"✓", "search"=>" compliance_failed "} 2016-03-31 22:21:58 [app] [W] Action failed | NoMethodError: undefined method `klass' for nil:NilClass | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/definition.rb:62:in `klass' | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/definition.rb:82:in `column' | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/definition.rb:96:in `type' | /opt/theforeman/tfm/root/usr/share/gems/gems/scoped_search-3.2.2/lib/scoped_search/definition.rb:214:in `block in default_fields_for' Version-Release number of selected component (if applicable): sat62-snap6 How reproducible: Steps to Reproduce: 1. try to search compliance reports with some criteria in the search box. 2. 3. Actual results: search throws a message on the UI. Oops, we're sorry but something went wrong undefined method `klass' for nil:NilClass Expected results: Search should be handled properly Search should not throw an error on the UI and traceback in the log file. Additional info:
Created redmine issue http://projects.theforeman.org/issues/14478 from this bug
Upstream bug assigned to szadok
I feel this should remain as a blocker for GA, as after running OSCAP for many hosts ( For example: 100+ or so ), if the user is unable to determine quickly what hosts are compliant and non-compliant, it really becomes difficult to get an idea about it.
VERIFIED With sat62-snap8.1 Had in total 2 compliance reports which had 9 passed and 29 failed Searched with compliance_failed > 28 and results shown had both the reports. Searched with compliance_passed > 8 and results shown had both the reports. Searched with compliance_failed > 29 and results shown had no reports. Searched with compliance_passed > 9 and results shown had no reports.
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:1501