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:
insights-client --test-connection fails when registered to external Capsule.
Version-Release number of selected component (if applicable):
- Satellite Server v6.11
- external Capsule Server v.611
- RHEL 8.6 host, provisioned by PXE/kickstart
How reproducible:
100%
Steps to Reproduce:
1. Register a client to external Capsule using the Global Registration Template ( Under Advanced section=> Setup Insights = yes )
2. Host registered successfully to the external capsule.
Actual results:
Insight client fails to establish the connection with the external capsule.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
GET https://capsule.example.com:443/redhat_access/r/insights/v1/branch_info
HTTP Status: 404 Not Found
HTTP Response Text: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body></html>
Running Connection Tests...
=== Begin Upload URL Connection Test ===
Testing: https://capsule.example.com:443/redhat_access/r/insights/uploads/
POST https://capsule.example.com:443/redhat_access/r/insights/uploads/
HTTP Status: 404 Not Found
HTTP Response Text: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body></html>
Connection failed
=== End Upload URL Connection Test: FAILURE ===
=== Begin API URL Connection Test ===
Testing: https://capsule.example.com:443/redhat_access/r/insights/
GET https://capsule.example.com:443/redhat_access/r/insights/
HTTP Status: 404 Not Found
HTTP Response Text: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body></html>
Connection failed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Expected results:
The test connection fails with a 404 error.
Additional info:
- Tried to register the host manually as well as using "Global Registration Template" and found the same behavior.
Workaround:-
Execute the command on the client to update the port:-
# subscription-manager config --server.port=8443
Satellite 6.11 introduced port 443 on Capsule's as the default port for client connections, 8443 is deprecated and will be removed in future releases. This appears that there is something about the Insights client traffic not getting properly proxied on 443 and needs some further investigation.
Eric,
I have uploaded this manifest manually into this machine into the Default Organization, but when I check now it was unloaded somehow as you mentioned, and when I uploaded manifest back there, tried registering a client against a external capsule, which installs/configures insights-client to successfully establish a connection with the external capsule, thought we hit this BZ 2129254 while registering same as Satellite
Thus, I confirm the setup error and move this BZ as verified.
Thanks
Gaurav
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.12 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-2022:8506