Bug 1322990
Summary: | compliance report searches fails | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Kedar Bidarkar <kbidarka> |
Component: | SCAP Plugin | Assignee: | Shlomi Zadok <szadok> |
Status: | CLOSED ERRATA | QA Contact: | Kedar Bidarkar <kbidarka> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | bbuckingham, ohadlevy, szadok |
Target Milestone: | Unspecified | Keywords: | 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
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 |