Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This is because you don't have latest smart_proxy_openscap, version 0.5.3
Please ensure Capsule / Proxy has latest smart_proxy_openscap, version 0.5.3
NOT_A_BUG, afaik
Yeah I have the latest version of, smart_proxy_openscap : 0.5.3-1
~]# rpm -qav rubygem-smart_proxy_openscap
rubygem-smart_proxy_openscap-0.5.3-1.el7sat.noarch
This package is required in Sattools repo and not in Sat6 repo.
Currently unavailable in Sattools repo.
On the "new host" we still see the old RPM.
~]# rpm -qav | grep -i foreman_scap
rubygem-foreman_scap_client-0.1.0.4-1.el7sat.noarch
I had tested it using the latest rpm and still face an issue,
but now the packaging issue is fixed , but the original issue mentioned in initial bug description still exists.
@Shlomi: Do we require this PR? https://github.com/theforeman/smart_proxy_openscap/pull/23/files
I face the same issue as mentioned in comment 15, also below are the packages installed when using sat62-snap7.1 build.
[root@katello1 ~]# rpm -qav | grep -ie scap
rubygem-smart_proxy_openscap-0.5.3.2-1.el7sat.noarch
perl-Pod-Escapes-1.04-286.el7.noarch
openscap-scanner-1.2.5-3.el7.x86_64
puppet-foreman_scap_client-0.3.3-10.el7sat.noarch
scap-security-guide-0.1.25-3.el7.noarch
rubygem-openscap-0.4.3-3.el7sat.noarch
openscap-1.2.5-3.el7.x86_64
tfm-rubygem-foreman_openscap-0.5.3.3-1.el7sat.noarch
[root@katello1 ~]# rpm -qav | grep -ie foreman-installer
foreman-installer-katello-3.0.0.17-1.el7sat.noarch
foreman-installer-1.11.0.1-1.el7sat.noarch
Applying the workaround as per comment 17 works fine.
TESTED With sat62-snap7.1 build.
Shlomi,
The indicated puppet-foreman_proxy changes should have been delivered with the version of foreman-installer indicated. Can you advise to figure out whether we are still missing a change or the verification steps just need updating to properly configure the system?
Eric,
I am not sure.
It seems that symlinks are not followed / permission not respected?
When setting the full paths at openscap.yml, everything seems to work okay
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