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:
With satellite 6.11, the client registered to the capsule server is using "443" as default for RHSM API. However when I run "insights-client", I found the API "https://<capsule-fqdn>:443/redhat_access/r/insights/v1/branch_info" return 404. So we can not get the satellite server information on the client now. It works with 8443.
Version-Release number of selected component (if applicable):
6.11.0
How reproducible:
every time
Steps to Reproduce:
1. deploy a satellite capsule 6.11.0
2. register a host to the capsule
3. run "insights-client"
4. check the "branch_info" file in the generated insights-archive
Actual results:
it is "{'remote_branch': -1, 'remote_leaf': -1}"
Expected results:
it should contain the right satellite version info like:
{"product": {"major_version": "6", "type": "Satellite", "minor_version": "11"}, "labels": [{"namespace": "satellite", "value": "Default Location", "key": "location"}, {"namespace": "satellite", "value": "Default Location", "key": "location"}, {"namespace": "satellite", "value": "all client hosts", "key": "hostgroup"}, {"namespace": "satellite", "value": "Capsule Client", "key": "hostgroup"}, {"namespace": "satellite", "value": "all client hosts/Capsule Client", "key": "hostgroup"}, {"namespace": "satellite", "value": "Default Organization", "key": "organization"}, {"namespace": "satellite", "value": "stage", "key": "lifecycle_environment"}, {"namespace": "satellite", "value": "view1", "key": "content_view"}, {"namespace": "satellite", "value": "key1", "key": "activation_key"}, {"namespace": "satellite", "value": "aec4ad37-1c17-4f5d-bd04-485f52601301", "key": "satellite_instance_id"}, {"namespace": "satellite", "value": "1", "key": "organization_id"}], "display_name": "Default Organization", "hostname": "huali-sat68.vm.gsslab.pek2.redhat.com", "remote_branch": "731be4c5-d3ea-4b7d-85c4-7724c28f9e8c", "organization_id": 1, "satellite_instance_id": "aec4ad37-1c17-4f5d-bd04-485f52601301", "remote_leaf": "9363c647-9319-49d7-9233-16660d67803e"}
Additional info:
Hi Brad,
I think it isn't. Because port "443" is supported in satellite 6.11. It is mentioned in the release note https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/release_notes/index#assembly_introducing-red-hat-satellite_sat6-release-notes:
New default port for communication with Red Hat Subscription Management (RHSM) API on Capsule servers
With this release, Capsule Servers accept communication for the RHSM API on port 443 by default. The formerly used port 8443 is now deprecated and remains open only for existing content hosts that do not get an automatic configuration update.
Before the capsule server use "8443" for the RHSM API. And it works well. So if it is an old client registered to satellite capsule, it still uses "8443" and the API works well. However, a new client registered to satellite capsule uses "443" now, and the API doesn't work, it returns "404".
Description of problem: With satellite 6.11, the client registered to the capsule server is using "443" as default for RHSM API. However when I run "insights-client", I found the API "https://<capsule-fqdn>:443/redhat_access/r/insights/v1/branch_info" return 404. So we can not get the satellite server information on the client now. It works with 8443. Version-Release number of selected component (if applicable): 6.11.0 How reproducible: every time Steps to Reproduce: 1. deploy a satellite capsule 6.11.0 2. register a host to the capsule 3. run "insights-client" 4. check the "branch_info" file in the generated insights-archive Actual results: it is "{'remote_branch': -1, 'remote_leaf': -1}" Expected results: it should contain the right satellite version info like: {"product": {"major_version": "6", "type": "Satellite", "minor_version": "11"}, "labels": [{"namespace": "satellite", "value": "Default Location", "key": "location"}, {"namespace": "satellite", "value": "Default Location", "key": "location"}, {"namespace": "satellite", "value": "all client hosts", "key": "hostgroup"}, {"namespace": "satellite", "value": "Capsule Client", "key": "hostgroup"}, {"namespace": "satellite", "value": "all client hosts/Capsule Client", "key": "hostgroup"}, {"namespace": "satellite", "value": "Default Organization", "key": "organization"}, {"namespace": "satellite", "value": "stage", "key": "lifecycle_environment"}, {"namespace": "satellite", "value": "view1", "key": "content_view"}, {"namespace": "satellite", "value": "key1", "key": "activation_key"}, {"namespace": "satellite", "value": "aec4ad37-1c17-4f5d-bd04-485f52601301", "key": "satellite_instance_id"}, {"namespace": "satellite", "value": "1", "key": "organization_id"}], "display_name": "Default Organization", "hostname": "huali-sat68.vm.gsslab.pek2.redhat.com", "remote_branch": "731be4c5-d3ea-4b7d-85c4-7724c28f9e8c", "organization_id": 1, "satellite_instance_id": "aec4ad37-1c17-4f5d-bd04-485f52601301", "remote_leaf": "9363c647-9319-49d7-9233-16660d67803e"} Additional info: