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.
DescriptionJaskaran Singh Narula
2019-02-05 14:14:13 UTC
Description of problem:
After creating SCAP policy with a number or name pattern and running the scan on the same and even on different client systems the compliance report does not show up if multiple policies is selected.
Version-Release number of selected component (if applicable):
rubygem-smart_proxy_openscap-0.6.11-1.el7sat.noarch
scap-security-guide-0.1.40-12.el7.noarch
perl-Pod-Escapes-1.04-294.el7_6.noarch
puppet-foreman_scap_client-0.3.16-3.el7sat.noarch
openscap-scanner-1.2.17-2.el7.x86_64
openscap-1.2.17-2.el7.x86_64
tfm-rubygem-foreman_openscap-0.10.3-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_openscap-0.1.6-1.el7sat.noarch
rubygem-openscap-0.4.7-3.el7sat.noarch
How reproducible:
Fully reproduceable.
Steps to Reproduce:
1. Simple setup of scap on satellite and on client system.
2. Make policies with names such as
a. 2019 New
b. 2019 New1
c. 2019 New2
d. 2019 standard New1
3. Apply the scan and run the scan on one single host or on different hosts.
4. After reports get uploaded search with below search options.
[1] last_for = host and policy ~ "2019" No result
[2] last_for = host and policy = "2019 New" and policy = "2019 New1" No result
[3] policy = "2019 New" and policy = "2019 New1" No result
Actual results:
No report comes up.
Expected results:
Reports associated with the profiles should show up.
Additional info:
Report always belongs to one policy and there can never be a report that has more that one policy. Because of that, condition 'policy = "2019 New" and policy = "2019 New1"' will always be false, so the examples [2] and [3] return correctly no results. Maybe the search meant to be 'policy = "2019 New" or policy = "2019 New1"'?
There is a bug in '~' operator, so example [1] returns incorrectly no results. Searching by exact match worked for me: 'last_for = host and policy ="2019 New"'
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/RHSA-2020:1454
Description of problem: After creating SCAP policy with a number or name pattern and running the scan on the same and even on different client systems the compliance report does not show up if multiple policies is selected. Version-Release number of selected component (if applicable): rubygem-smart_proxy_openscap-0.6.11-1.el7sat.noarch scap-security-guide-0.1.40-12.el7.noarch perl-Pod-Escapes-1.04-294.el7_6.noarch puppet-foreman_scap_client-0.3.16-3.el7sat.noarch openscap-scanner-1.2.17-2.el7.x86_64 openscap-1.2.17-2.el7.x86_64 tfm-rubygem-foreman_openscap-0.10.3-1.el7sat.noarch tfm-rubygem-hammer_cli_foreman_openscap-0.1.6-1.el7sat.noarch rubygem-openscap-0.4.7-3.el7sat.noarch How reproducible: Fully reproduceable. Steps to Reproduce: 1. Simple setup of scap on satellite and on client system. 2. Make policies with names such as a. 2019 New b. 2019 New1 c. 2019 New2 d. 2019 standard New1 3. Apply the scan and run the scan on one single host or on different hosts. 4. After reports get uploaded search with below search options. [1] last_for = host and policy ~ "2019" No result [2] last_for = host and policy = "2019 New" and policy = "2019 New1" No result [3] policy = "2019 New" and policy = "2019 New1" No result Actual results: No report comes up. Expected results: Reports associated with the profiles should show up. Additional info: