Description of problem: running foreman-installer --help does not list --enable-foreman-plugin-openscap and --enable-foreman-proxy-plugin-openscap arguments so I can't install openscap plugin. It's not present in either of capsule and katello scenarios. Version-Release number of selected component (if applicable): 6.2 beta snap4 foreman-installer-katello-3.0.0.3-1.el7sat.noarch How reproducible: always Steps to Reproduce: 1. try to install openscap plugin 2. 3. Actual results: there are no options for it Expected results: openscap plugin is installed Additional info:
Created redmine issue http://projects.theforeman.org/issues/14327 from this bug
Upstream bug assigned to mhulan
Moving to POST since upstream bug http://projects.theforeman.org/issues/14327 has been closed ------------- Marek Hulán Applied in changeset commit:katello-installer|8208868751c672c2696b6ec8aea34dcaf6123d3b.
Verified in Satellite 6.2 Beta Snap 6 Compose 2. [root@rhsm-qe-1 ~]# foreman-installer --help | grep scap --[no-]enable-foreman-plugin-openscap Enable 'foreman_plugin_openscap' puppet module (default: false) --[no-]enable-foreman-proxy-plugin-openscap Enable 'foreman_proxy_plugin_openscap' puppet module (default: false) = Module foreman_plugin_openscap: --foreman-plugin-openscap-configure-openscap-repo Enable custom yum repo with packages needed for foreman_openscap, (default: true) = Module foreman_proxy_plugin_openscap: --foreman-proxy-plugin-openscap-enabled enables/disables the plugin (default: true) --foreman-proxy-plugin-openscap-listen-on Proxy feature listens on http, https, or both (default: "https") --foreman-proxy-plugin-openscap-openscap-send-log-file Log file for the forwarding script (default: "/var/log/foreman-proxy/openscap-send.log") --foreman-proxy-plugin-openscap-spooldir Directory where OpenSCAP audits are stored before they are forwarded to Foreman (default: "/var/spool/foreman-proxy/openscap") --foreman-proxy-plugin-openscap-version plugin package version, it's passed to ensure parameter of package resource
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:1500