Bug 1861656

Summary: smart-proxy-openscap-send command fails to upload reports to satellite.
Product: Red Hat Satellite Reporter: Jameer Pathan <jpathan>
Component: SCAP PluginAssignee: Ondřej Pražák <oprazak>
Status: CLOSED ERRATA QA Contact: Jameer Pathan <jpathan>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.8.0CC: mhulan, oprazak, pcreech
Target Milestone: 6.8.0Keywords: Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-smart_proxy_openscap-0.7.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:04:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1332702    

Description Jameer Pathan 2020-07-29 07:29:08 UTC
Description of problem:
smart-proxy-openscap-send command fails to upload reports to satellite.

Version-Release number of selected component (if applicable):
- Satellite 6.8.0 snap 10

How reproducible:
Always

Steps to Reproduce:
1. Have few scap reports available in spool directory.
2. Run "smart-proxy-openscap-send" command.

Actual results:
# smart-proxy-openscap-send
/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': /usr/share/foreman-proxy/lib/launcher.rb:81: syntax error, unexpected '.' (SyntaxError)
      Proxy::SETTINGS.tls_disabled_versions&.each do |version|
                                             ^
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/share/foreman-proxy/lib/smart_proxy_main.rb:4:in `<top (required)>'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require'
	from /usr/bin/smart-proxy-openscap-send:16:in `<main>'

Expected results:
- Reports are successfully uploaded to Satellite server.

Additional info:

Comment 1 Ondřej Pražák 2020-07-29 08:33:52 UTC
Created redmine issue https://projects.theforeman.org/issues/30514 from this bug

Comment 2 Bryan Kearney 2020-07-29 12:05:53 UTC
Upstream bug assigned to oprazak

Comment 3 Bryan Kearney 2020-07-29 12:05:56 UTC
Upstream bug assigned to oprazak

Comment 4 Bryan Kearney 2020-07-30 12:05:48 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30514 has been resolved.

Comment 5 Jameer Pathan 2020-09-03 12:00:23 UTC
Verified

Verified with:
- Satellite 6.8.0 snap 13

Test steps:
1. Have few scap reports available in spool directory.
2. Run "smart-proxy-openscap-send" command.

Observations:
- Reports are successfully uploaded to Satellite server.

Comment 8 errata-xmlrpc 2020-10-27 13:04:48 UTC
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 (Important: Satellite 6.8 release), 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-2020:4366