Bug 1655734

Summary: Scap report shows passed results under failed only list.
Product: Red Hat Satellite Reporter: Jaskaran Singh Narula <janarula>
Component: SCAP PluginAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Sanket Jagtap <sjagtap>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.3CC: mhulan, oprazak
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-12-04 07:26:17 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 Jaskaran Singh Narula 2018-12-03 19:31:16 UTC
Description of problem:
Scap report shows passed results as well when you select failed only list on the Satellite 6.3  web ui. 

Version-Release number of selected component (if applicable):


How reproducible:
Fully reproducible. 

Steps to Reproduce:
1. Configure SCAP on Red Hat Satellite 6.3 
2. Upload the default scap content.
3. Make a policy for RHEL 7 systems with Standard System Security Profile for Red Hat Enterprise Linux 7  profile. 

4. run puppet agent -tv on client system 
5. foreman_scap_client <policy ID> 

Actual results:
The report on Satellite web ui shows some of the passed results as well under the list of Failed only list. 

Expected results:
It should not show any passed results under the list of failed ones.  

Additional info:
[1] The issue is reproduced under the mentioned credentials. 

[2] Also, the same issue is not visible in Satellite 6.4

Comment 4 Ondřej Pražák 2018-12-04 07:26:17 UTC
Thank you for reporting this bug. We already track a similar item as BZ #1418859 which was fixed in 6.4. The fact that you were not able to reproduce on 6.4 suggests this is a duplicate, therefore I will close. Feel free to reopen if I misunderstood or if the problem appears again on 6.4 or on any newer version.

*** This bug has been marked as a duplicate of bug 1418859 ***