Description of problem: Default OSCAP content not available even after installing the below packages: 1)'tfm-rubygem-foreman_openscap'. 2) 'scap-security-guide'. Also running "foreman-rake db:seed" also doesn't populate it and shows the below info: ## SCAP content is invalid: No Proxy with OpenScap features ## ## SCAP content is invalid: No Proxy with OpenScap features ## ## SCAP content is invalid: No Proxy with OpenScap features ## ## SCAP content is invalid: No Proxy with OpenScap features ## Version-Release number of selected component (if applicable): Sat6.2.0-Beta-SNAP1 How reproducible: Steps to Reproduce: 1. Install oscap packages 2. Navigate to "oscap content" page under "hosts" --> "compliance". 3. Observe no default oscap-content. Actual results: No "Default OSCAP Content" available. Expected results: Require "Default OSCAP Content" under "oscap content" page. Additional info:
Found a workaround after installing package "rubygem-smart_proxy_openscap-0.5.3-1.el7sat.noarch" Workaround: Ran "foreman-rake db:seed".
Created redmine issue http://projects.theforeman.org/issues/14061 from this bug
Upstream bug component is Provisioning
Upstream bug component is SCAP Plugin
Fixed with https://github.com/theforeman/foreman_openscap/pull/152
Moving to POST since upstream bug http://projects.theforeman.org/issues/14061 has been closed ------------- Shlomi Zadok Merged as https://github.com/theforeman/foreman_openscap/commit/12ab8ee2a9e6e974271b1d9bcb29fdc32ac51bcf
Wondering can the below steps, a) restarting smart-proxy service, b) capsule feature-refresh c) foreman-rake foreman_openscap:bulk_upload:default, be part of installing the rubygem-smart_proxy_openscap-0.5.3-1.el7sat.noarch.rpm itself, that would help a lot in avoiding those multiple steps. So, currently trying to do a), b) and c) manually work as mentioned in comment9. VERIFIED With Sat62-snap5
RFE, so that installing rubygem-smart_proxy_openscap-0.5.3-1.el7sat.noarch.rpm package should populate the "Default OSCAP content". I believe running rake commands should not be required.
I dont think thats feasible, as you might not run on the same machine, so on capsule install it should expect foreman packages to be present. IMHO a better RFE would be to enhance the installer upgrade scenario to include this work after packages and configuration files are in place (and service is running etc).
Yes this is VERIFIED but had then converted this to RFE. But as mentioned in comment 13, I think this needs to be tracked for upgrade scenario of OSCAP. But if we need a new bug to track this for upgrade scenario we can close this and raise a new one.
Update: I think the idea here is, atleast for users who are upgrading their setups with the OSCAP plugin enabled, shouldn't have to run "foreman-rake foreman_openscap:bulk_upload:default".
When using a *NEW* installation we need to run "foreman-rake foreman_openscap:bulk_upload:default" to generate *NEW* default SCAP content. This issue was verified already at comment #15 For Upgrading from Sat 6.1: 1. If you already have default SCAP content - you need to do nothing. 2. If you don't have default SCAP content, and you want RH default SCAP content - then you can run "foreman-rake foreman_openscap:bulk_upload:default" Not sure why this issue requires a new RFE? (It may be a documentation step, though)
Hi Bryan, Thank you for the needinfo request, and my apologies for the delay in providing a response. This is not currently included in the documentation, but looks like an easy fix. We'll triage this out shortly. Kind regards, Andrew
Assigning to Russell for review.
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