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):
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
SCAP content is not shown if your context is not 'Any Context.
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.
Created redmine issue http://projects.theforeman.org/issues/11744 from this bug
Proposed fix: https://github.com/theforeman/foreman_openscap/pull/127
Moving to POST since upstream bug http://projects.theforeman.org/issues/11744 has been closed
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.