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.
DescriptionBrad Buckingham
2022-01-21 20:04:55 UTC
+++ This bug was initially created as a clone of Bug #2043081 +++
Description of problem:
When running insights-client --compliance on a machine that is connected to Satellite, the request will fail with status 406.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. run insights-client --compliance
2.
3.
Actual results:
Observe the error
Expected results:
Request succeeds
Additional info:
This is caused by mime-type header not being passed correctly by the request forwarder in rh_cloud plugin.
Verified:
Verified with:
- Satellite 6.10.3 snap 1
- insights-client-3.0.13-1.el8_1.noarch
- insights-client-3.1.7-1.el8_5.noarch
Test steps:
- Register a satellite content host with insights.
- Install scap-security-guide, openscap-scanner and openscap packages on host.
- Go to console.redhat.com
- Go to compliance > SCAP Polices > Create new policy (on C.R.C)
- Create a new compliance policy for the insights host
- Run "insights-client --compliance" on host.
Observation:
- "insights-client --compliance" completed successfully.
- Results/Reports appeared on C.R.C
[root@dhcp-2-169 ~]# insights-client --compliance
System uses SSG version 0.1.48
Running scan for xccdf_org.ssgproject.content_profile_stig... this may take a while
Uploading Insights data.
Successfully uploaded report for dhcp-2-169.vms.sat.rdu2.redhat.com.
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 (Low: Satellite 6.10.3 Async Bug Fix 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-2022:0790