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.
Description of problem: When setting up OpenSCAP, the RPM installation adds in the default content from the scap-security-guide. However, as it is not associated with any organization, the end user has to switch to 'Any Context' to see it, which is confusing.
Version-Release number of selected component (if applicable):
openscap-1.2.4-1.el7sat.x86_64
openscap-scanner-1.2.4-1.el7sat.x86_64
puppet-foreman_scap_client-0.3.3-9.el7sat.noarch
ruby193-rubygem-foreman_openscap-0.3.2.10-1.el7sat.noarch
ruby193-rubygem-openscap-0.4.2-2.el7sat.noarch
ruby193-rubygem-scaptimony-0.3.0.1-1.el7sat.noarch
rubygem-smart_proxy_openscap-0.3.0.9-1.el7sat.noarch
scap-security-guide-0.1.19-2.el7.noarch
How reproducible:
100%
Steps to Reproduce:
1.Install the SCAP components;
yum install ruby193-rubygem-foreman_openscap -y
2. Restart Apache
service httpd restart
3. Go to hosts->SCAP Contents
Actual results:
SCAP content is not shown if your context is not 'Any Context.
Expected results:
It is the end-users expectation that if they installed the SCAP components, they'd want to use them. As such, this BZ requests that the SCAP content is associated with all organizations that are present on the Satellite at the time the SCAP plugin is enabled.
Additional info:
For Sat6.2, after doing the below steps the OpenSCAP content can be seen associated with "Default Organization".
a) Installing foreman-rake foreman_openscap:bulk_upload:default
b) Restarting smart-proxy service
c) capsule feature-refresh
d) foreman-rake foreman_openscap:bulk_upload:default
VERIFIED With Sat62-snap6
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