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.
Bug 1984550 - insights-client --test-connection fails when using general "HTTP(S) proxy" setting of satellite.
Summary: insights-client --test-connection fails when using general "HTTP(S) proxy" se...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: RH Cloud - Inventory
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.9.6
Assignee: Shimon Shtein
QA Contact: Jameer Pathan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-21 15:24 UTC by James Jeffers
Modified: 2021-09-21 14:37 UTC (History)
7 users (show)

Fixed In Version: 3.0.26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1973285
Environment:
Last Closed: 2021-09-21 14:37:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2021:3628 0 None None None 2021-09-21 14:37:41 UTC

Comment 1 Ashish Humbe 2021-07-26 18:32:03 UTC 
FAILED QA 


# insights-client --test-connection --net-debug
GET https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/v1/branch_info
GET branch_info status: 200
Running Connection Tests...
=== Begin Upload URL Connection Test ===
Testing: https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/uploads/
HTTP Status Code: 200
HTTP Status Text: OK
HTTP Response Text: 
Successfully connected to: https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/uploads/
=== End Upload URL Connection Test: SUCCESS ===

=== Begin API URL Connection Test ===
Testing: https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/
HTTP Status Code: 500
HTTP Status Text: Internal Server Error
HTTP Response Text: {}
Connection failed
=== End API URL Connection Test: FAILURE ===

Connectivity tests completed with some errors
See /var/log/insights-client/insights-client.log for more details.



Insights client registration was successful via proxy but --test-connection failed with ISE.
Comment 3 Ashish Humbe 2021-07-27 10:25:34 UTC 
When we use legacy_upload = False option in the /etc/insights-client/insights-client.conf I see the --test-connection works properly


# insights-client --test-connection --net-debug
GET https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/v1/branch_info
GET branch_info status: 200
Running Connection Tests...
=== Begin Upload URL Connection Test ===
Testing https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/platform/ingress/v1/upload
HTTP Status Code: 202
HTTP Status Text: Accepted
HTTP Response Text: {"request_id":"12b555601eda4fb48bc624d0a2f0d463","upload":{"account_number":"540155"}}
Successfully connected to: https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/platform/ingress/v1/upload
=== End Upload URL Connection Test: SUCCESS ===

=== Begin API URL Connection Test ===
Testing https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/platform/apicast-tests/ping
HTTP Status Code: 200
HTTP Status Text: OK
HTTP Response Text: {"status":"available"}
Successfully connected to: https://dhcp130-146.gsslab.pnq2.redhat.com:443/redhat_access/r/insights/platform/apicast-tests/ping
=== End API URL Connection Test: SUCCESS ===

Connectivity tests completed successfully
See /var/log/insights-client/insights-client.log for more details.
Comment 6 Jameer Pathan 2021-09-06 11:47:49 UTC 
Verified:

Verified with:
- Satellite 6.9.6 snap 1
- tfm-rubygem-foreman_rh_cloud-3.0.26-1.el7sat.noarch

Test steps:
- Try registering content host with insights(with and without Default HTTP Proxy configured on satellite).

Observation:
- insights-client registration process finished successfully.
- "insights-client --test-connection" worked as expected.
Comment 11 errata-xmlrpc 2021-09-21 14:37:26 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 (Satellite 6.9.6 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/RHBA-2021:3628
Note You need to log in before you can comment on or make changes to this bug.