Red Hat Bugzilla – Bug 1194178
oscap client packages needed in rhcommon repository
Last modified: 2017-02-23 15:28:40 EST
Description of problem: There are couple of oscap packages which are required in rhcommon repository. a) rubygem-foreman_scap_client b) openscap c) openscap-utils d) openscap-scanner I might be missing other packages and dependencies which also may need to be moved. For example from the descriptions of the rpms: [root@xxxx ~]# rpm -qpi rubygem-foreman_scap_client-0.1.0-1.el6_6sat.noarch.rpm | grep -A 2 Description Description : Client script that runs OpenSCAP scan and uploads the result to foreman proxy. Version-Release number of selected component (if applicable): sat6.1 Beta-snap3-compose1 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: the mentioned packages are not available via the rhcommon repo currently and exist in satellite6 repo. Expected results: the above mentioned packages are needed in rhcommon repo, as these will be required to install on the hosts[systems]. Additional info: I am not 100% sure but looks like if we are providing openscap related packages for the clients then they need to be provided in someway to the clients too.
openscap-* packages are present in RHEL base channel (*), no need to push them to the client repository. rubygem-foreman_scap_client is, on the other hand, supposed and required to be run on the client. --- (*) We need openscap-1.2.1 only on the Satellite server. On the clients we just need any version of openscap-* packages. Hence taking openscap packages from rhel channel is 0k for clients.
What about RHEL 5? Will this gem work on RHEL 5? I have not even tried to build it yet.
We now have the below packages in RHEL7 and RHEL6 rhcommon repository. a) rubygem-foreman_scap_client-0.1.0-1.el7sat.noarch.rpm [for RHEL7] b) rubygem-foreman_scap_client-0.1.0-1.el6_6sat.noarch.rpm [for RHEL6]
VERIFIED with sat6.1 beta snap5.
This bug is slated to be released with Satellite 6.1.
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/RHSA-2015:1592