Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1322990 - compliance report searches fails
compliance report searches fails
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: SCAP Plugin (Show other bugs)
6.2.0
Unspecified Unspecified
unspecified Severity high (vote)
: Beta
: Unused
Assigned To: Shlomi Zadok
Kedar Bidarkar
http://projects.theforeman.org/issues...
: Triaged
Depends On:
Blocks:
  Show dependency tree / graph
 
Reported: 2016-03-31 17:16 EDT by Kedar Bidarkar
Modified: 2016-07-27 05:30 EDT (History)
3 users (show)

See Also:
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 05:30:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 14478 None None None 2016-04-06 11:20 EDT
Foreman Issue Tracker 14504 None None None 2016-04-06 11:02 EDT
Red Hat Product Errata RHBA-2016:1501 normal SHIPPED_LIVE Red Hat Satellite 6.2 Capsule and Server 2016-07-27 08:28:58 EDT

  None (edit)
Description Kedar Bidarkar 2016-03-31 17:16:20 EDT 
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 09:01:17 EDT 
Created redmine issue http://projects.theforeman.org/issues/14478 from this bug
Comment 4 Bryan Kearney 2016-04-05 10:11:46 EDT 
Upstream bug assigned to szadok@redhat.com
Comment 5 Kedar Bidarkar 2016-04-05 12:07:55 EDT 
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 11:32:00 EDT 
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 05:30:00 EDT 
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
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.