Description of Problem:

Failed to connect insights on RHEL-9.5.0-20240519.9_ppc64le with proxy

Please provide the package NVR for which bug is seen:

insights-client-3.2.2-3.el9.noarch

How reproducible

Always

Is this a regression issue:

( Yes/No) 

Steps to Reproduce

• [Step 1] Register RHEL-9.5.0-20240519.9_ppc64le against Satellite
• [root@ibm-p9z-23-lp3 integration-tests]#

subscription-manager register --activationkey="everything-ak" --org="INSIGHTS_QA_6089719_REM"

• [Step 2] Set proxy in insights-client.conf:

[root@ibm-p9z-23-lp3 integration-tests]# cat /etc/insights-client/insights-client.conf | grep -E "proxy|legacy"

1. URL for your proxy.  Example: http://user:pass@192.168.100.50:8080

proxy=http://auto-services.usersys.redhat.com:3129

legacy_upload=False

• [Step 3] Check connection

[root@ibm-p9z-23-lp3 integration-tests]# insights-client --test-connection

GET https://ci-vm-10-0-138-107.hosted.upshift.rdu2.redhat.com:443/redhat_access/r/insights/v1/branch_info

Could not auto configure, falling back to static config

See /var/log/insights-client/insights-client.log for additional information

Running Connection Tests...

=== Begin Upload URL Connection Test ===

Testing https://cert-api.access.redhat.com/r/insights/platform/ingress/v1/upload

POST https://cert-api.access.redhat.com/r/insights/platform/ingress/v1/upload

Could not successfully connect to: https://cert-api.access.redhat.com/r/insights/platform/ingress/v1/upload

HTTPSConnectionPool(host='cert-api.access.redhat.com', port=443): Max retries exceeded with url: /r/insights/platform/ingress/v1/upload (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(104, 'Connection reset by peer')))

HTTPSConnectionPool(host='cert-api.access.redhat.com', port=443): Max retries exceeded with url: /r/insights/platform/ingress/v1/upload (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(104, 'Connection reset by peer')))

Connectivity test failed! Please check your network configuration

Additional information may be in /var/log/insights-client/insights-client.log

[root@ibm-p9z-23-lp3 integration-tests]# insights-client --register

Could not auto configure, falling back to static config

See /var/log/insights-client/insights-client.log for additional information

Could not auto configure, falling back to static config

See /var/log/insights-client/insights-client.log for additional information

Unable to fetch egg url https://cert-api.access.redhat.com/r/insights/platform/module-update-router/v1/channel?module=insights-core: HTTPSConnectionPool(host='cert-api.access.redhat.com', port=443): Max retries exceeded with url: /r/insights/platform/module-update-router/v1/channel?module=insights-core (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(104, 'Connection reset by peer'))). Defaulting to /release

HTTPSConnectionPool(host='cert-api.access.redhat.com', port=443): Max retries exceeded with url: /r/insights/v1/static/release/insights-core.egg (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(104, 'Connection reset by peer')))

The Insights API could not be reached.

Could not auto configure, falling back to static config

See /var/log/insights-client/insights-client.log for additional information

HTTPSConnectionPool(host='cert-api.access.redhat.com', port=443): Max retries exceeded with url: /r/insights/platform/inventory/v1/hosts?insights_id=78e62f89-626f-42aa-a88c-dbc1839da723 (Caused by ProxyError('Cannot connect to proxy.', ConnectionResetError(104, 'Connection reset by peer')))

The Insights API could not be reached.

Actual Behavior

As step 3, can not connect to insights with proxy

Expected Behavior

Insights registration with proxy should be successful.

Additional info

no issues on RHEL-9.5.0-20240519.9_x86_64