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.
DescriptionDeepannagaraj Nagarathinam
2017-12-18 20:52:50 UTC
Description of problem:
- On the Compliance Reports page, when selecting the Failed only option in the "Show log messages" field, it still shows some of the passed conditions.
Version-Release number of selected component (if applicable):
- Red Hat Satellite 6.3
How reproducible:
- Always
Steps to Reproduce:
1. Configure OpenSCAP and generate reports.
2. On the Compliance Reports page, select the Failed Only option.
Actual results:
- Some of the passed results are also showing up.
Expected results:
- Only the failed reports should be displayed.
Additional info:
I believe that has already been tracked under BZ 1418859, please search for existing reports before opening new, thank you.
*** This bug has been marked as a duplicate of bug 1418859 ***