Description of problem: Uploading results while running 'foreman_scap_client policy_id' fails on the client ~]# foreman_scap_client 1 DEBUG: running: oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_common --results-arf /tmp/d20160302-23771-1bw0t40/results.xml /var/lib/openscap/content/96c2a9d5278d5da905221bbb2dc61d0ace7ee3d97f021fccac994d26296d986d.xml DEBUG: running: /usr/bin/bzip2 /tmp/d20160302-23771-1bw0t40/results.xml Uploading results to https://test.redhat.com:9090/compliance/arf/1 <!DOCTYPE html> <html> <head> <style type="text/css"> body { text-align:center;font-family:helvetica,arial;font-size:22px; color:#888;margin:20px} #c {margin:0 auto;width:500px;text-align:left} </style> </head> <body> <h2>Sinatra doesn’t know this ditty.</h2> <img src='https://test.redhat.com:9090/compliance/__sinatra__/404.png'> <div id="c"> Try this: <pre>put '/arf/1' do "Hello World" end</pre> </div> </body> </html> Upload failed: 404 "Not Found " Version-Release number of selected component (if applicable): Sat6.2.0-Beta-SNAP1 How reproducible: Steps to Reproduce: 1. Run the command 'foreman_scap_client <policy_id>' on the client/host. 2. 3. Actual results: uploading results fails Expected results: uploading of results should be successful Additional info: Upstream issue raised, http://projects.theforeman.org/issues/13514
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
Looks like this does need to get included in a downstream bu ild
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.
MOving to POST based on Comment 19 and 20.
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
Created redmine issue http://projects.theforeman.org/issues/14621 from this bug
Suggested fix: https://github.com/theforeman/smart_proxy_openscap/pull/28
Upstream bug component is Uncategorized
Upstream bug assigned to szadok
VERIFIED with sat62-snap9 Now while running 'foreman_scap_client <policy_id>' the scan runs successfully and no errors seen.
Re-opening this bug as this issue is now seen with snap11.0 , tested with Sat6 on RHEL6.
Created attachment 1158338 [details] unable to upload reports
I reproduced on RHEL6 and submitted patch to the upstream: https://github.com/theforeman/smart_proxy_openscap/pull/33
Build:Satellite 6.2 snap 14.1 Reports were generated and send to respective Openscap Capsule foreman_scap_client policy_id' was successfull
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