Hide Forgot
Description of problem: oscap installation failed using installer options Version-Release number of selected component (if applicable): satellite-6.2.0-9.0.beta.el6sat.noarch How reproducible: Always Steps to Reproduce: 1. foreman-installer --enable-foreman-plugin-openscap --enable-foreman-proxy-plugin-openscap Actual results: Output from Jenkins QE automation job: 99%] [] /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: Failed to call refresh: Could not start Service[foreman-proxy]: Execution of '/sbin/service foreman-proxy start' returned 1: Starting foreman-proxy: [FAILED] out: Installing Error: /Stage[main]/Foreman_proxy::Service/Service [99%] [] /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: Could not start Service[foreman-proxy]: Execution of '/sbin/service foreman-proxy start' returned 1: Starting foreman-proxy: [FAILED] 99%] [] Execution of '/usr/bin/yum -d 0 -e 0 -y install tfm-rubygem-foreman_openscap' returned 1: Error Downloading Packages: out: Installing Error: Execution of '/usr/bin/yum -d 0 -e 0 -y ins [99%] [] /Stage[main]/Foreman::Plugin::Openscap/Foreman::Plugin[openscap]/Package[tfm-rubygem-foreman_openscap]/ensure: change from absent to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install tfm-rubygem-foreman_openscap' returned 1: Error Downloading Packages: Something went wrong! Check the log for ERROR-level output The full log is at /var/log/foreman-installer/katello.log Expected results: oscap is installed with no error Additional info:
Note: This error is found only in rhel 6 and rhel 7 works fine.
Note: This is not related to installer options, installing the oscap packages directly failed too.
OSCAP installation is successful now on rhel6 VERIFIED with sat62-snap12.1
*** Bug 1333107 has been marked as a duplicate of this bug. ***
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