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.

Bug 1322990

Summary: compliance report searches fails
Product: Red Hat Satellite Reporter: Kedar Bidarkar <kbidarka>
Component: SCAP PluginAssignee: Shlomi Zadok <szadok>
Status: CLOSED ERRATA QA Contact: Kedar Bidarkar <kbidarka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, ohadlevy, szadok
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14478
Whiteboard:
Fixed In Version: rubygem-foreman_openscap-0.5.3.4-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:30:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kedar Bidarkar 2016-03-31 21:16:20 UTC
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:

Comment 2 Shlomi Zadok 2016-04-05 13:01:17 UTC
Created redmine issue http://projects.theforeman.org/issues/14478 from this bug

Comment 4 Bryan Kearney 2016-04-05 14:11:46 UTC
Upstream bug assigned to szadok

Comment 5 Kedar Bidarkar 2016-04-05 16:07:55 UTC
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.

Comment 9 Kedar Bidarkar 2016-04-15 15:32:00 UTC
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.

Comment 11 errata-xmlrpc 2016-07-27 09:30:00 UTC
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