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.
Description of problem:
When the customer runs an OpenSCAP scan against their RHEL 8 hosts, the scan fails.
Version-Release number of selected component (if applicable):
Satellite server:
satellite-6.9.2-1.el7sat.noarch
redhat-release-server-7.9-6.el7_9.x86_64
Example Host:
redhat-release-8.4-0.6.el8.x86_64
rubygem-foreman_scap_client-0.4.7-1.el8sat.noarch
How reproducible:
100%
Steps to Reproduce:
1.
2.
3.
Actual results:
When the customer runs an OpenSCAP command against some of their servers, they get these errors:
1: DEBUG: running: oscap xccdf eval --profile PROFILE_NAME --results-arf /tmp/d20210714-16213-1fn07xw/results.xml /var/lib/openscap/content/b7772a4001f865517e30762c406dee80fdab2100ecc010f4408519a979665f6e.xml
2: Traceback (most recent call last):
3: 8: from /usr/bin/foreman_scap_client:23:in `<main>'
4: 7: from /usr/bin/foreman_scap_client:23:in `load'
5: 6: from /usr/share/gems/gems/foreman_scap_client-0.4.7/bin/foreman_scap_client:10:in `<top (required)>'
6: 5: from /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:22:in `run'
7: 4: from /usr/share/ruby/tmpdir.rb:93:in `mktmpdir'
8: 3: from /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:24:in `block in run'
9: 2: from /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:53:in `scan'
10: 1: from /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:60:in `run_scan'
11: /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:60:in `split': invalid byte sequence in UTF-8 (ArgumentError)
12: 13:
Exit status: 1
Expected results:
The scan should succeed on RHEL 8 hosts.
Additional info:
The error seems to arise from line 60 in this file (two are listed here because the problem was found in two different versions):
file version in the testing environment: /usr/share/gems/gems/foreman_scap_client-0.4.6/lib/foreman_scap_client/client.rb
file version in the customer environment: /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb
This is line 60, which appears to be identical in both versions of that file:
puts error_str.split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n")
We were able to resolve this issue in three different ways during testing:
puts line.scrub('').split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n")
puts error_str #.split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n")
#puts error_str.split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n")
Our customer tried the first fix, and it worked for them on multiple hosts:
puts line.scrub('').split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n")
I believe that this line fails because it's trying to process files in (subdirectories of) /var/lib/foreman-proxy/openscap/ that contain UTF characters (or perhaps invalid UTF characters).
Based on what I have tested...
Install the foreman_scap_client package on your hosts.
# yum install rubygem-foreman_scap_client --assumeyes
The above package creates/restores file: /usr/share/gems/gems/foreman_scap_client-0.5.1/lib/foreman_scap_client/base_client.rb
comment line 84, to ensure oscap scans continue to work because if you reinstall package rubygem-foreman_scap_client, the comment in line 84 will be removed.
I have not tested in RHEL 8, but On RHEL 7 and RHEL 9 systems it is line: **84** in file /usr/share/gems/gems/foreman_scap_client-0.5.1/lib/foreman_scap_client/base_client.rb
To gather scans from the Satellite web UI:
Step 1: Navigate to Hosts> Select Action>drop_down> Run All Ansible roles.
Step 2: Navigate to Hosts> Select desired host> Schedule a job>drop_down> Run OpenScap Scan. Wait until job completes.
Step 3: Navigate to Hosts> Compliance>Reports.
Likewise, execute the command below from the hosts and the report will be uploaded to the Satellite Web UI. The number '1' is the Scap Scan Policy number created in Satellite.
# /usr/bin/foreman_scap_client 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 (Important: Satellite Client Async Security Update), 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-2024:2011
Description of problem: When the customer runs an OpenSCAP scan against their RHEL 8 hosts, the scan fails. Version-Release number of selected component (if applicable): Satellite server: satellite-6.9.2-1.el7sat.noarch redhat-release-server-7.9-6.el7_9.x86_64 Example Host: redhat-release-8.4-0.6.el8.x86_64 rubygem-foreman_scap_client-0.4.7-1.el8sat.noarch How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: When the customer runs an OpenSCAP command against some of their servers, they get these errors: 1: DEBUG: running: oscap xccdf eval --profile PROFILE_NAME --results-arf /tmp/d20210714-16213-1fn07xw/results.xml /var/lib/openscap/content/b7772a4001f865517e30762c406dee80fdab2100ecc010f4408519a979665f6e.xml 2: Traceback (most recent call last): 3: 8: from /usr/bin/foreman_scap_client:23:in `<main>' 4: 7: from /usr/bin/foreman_scap_client:23:in `load' 5: 6: from /usr/share/gems/gems/foreman_scap_client-0.4.7/bin/foreman_scap_client:10:in `<top (required)>' 6: 5: from /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:22:in `run' 7: 4: from /usr/share/ruby/tmpdir.rb:93:in `mktmpdir' 8: 3: from /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:24:in `block in run' 9: 2: from /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:53:in `scan' 10: 1: from /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:60:in `run_scan' 11: /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb:60:in `split': invalid byte sequence in UTF-8 (ArgumentError) 12: 13: Exit status: 1 Expected results: The scan should succeed on RHEL 8 hosts. Additional info: The error seems to arise from line 60 in this file (two are listed here because the problem was found in two different versions): file version in the testing environment: /usr/share/gems/gems/foreman_scap_client-0.4.6/lib/foreman_scap_client/client.rb file version in the customer environment: /usr/share/gems/gems/foreman_scap_client-0.4.7/lib/foreman_scap_client/client.rb This is line 60, which appears to be identical in both versions of that file: puts error_str.split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n") We were able to resolve this issue in three different ways during testing: puts line.scrub('').split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n") puts error_str #.split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n") #puts error_str.split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n") Our customer tried the first fix, and it worked for them on multiple hosts: puts line.scrub('').split("\n").select { |item| item.start_with?('WARNING:') || item.start_with?('Downloading') }.join("\n") I believe that this line fails because it's trying to process files in (subdirectories of) /var/lib/foreman-proxy/openscap/ that contain UTF characters (or perhaps invalid UTF characters).