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:
As explained in https://bugzilla.redhat.com/show_bug.cgi?id=2247445 right now, If I want to use GRT and register a system with the Satellite server directly then, I need to ensure that the system can connect both on port 443 as well as 80 of the satellite.
But if someone is not using satellite for provisioning at all, They would want an incoming connection on port 80 to be disabled for security reasons. And that would cause the registration to fail at the end.
This is because, at the very end of registration, This API "GET /unattended/built?token=<token here>" is executed to update the build status of the host and it always targets port 80 of the satellite over HTTP.
Version-Release number of selected component (if applicable):
Any Supported version of Satellite ( 6.11 - 6.14 )
How reproducible:
Always and Easily
Steps to Reproduce:
1. Install and Configure a Satellite so that a system can be registered with it.
2. Block incoming access on port 80 of the satellite
3. Try registering a host with the satellite via the GRT method and observe till the end.
Actual results:
* Host is registered fine and yum is working as well
* The Host never came out of Build mode because the `/unattended/built` endpoint failed to execute.
* Due to this, No facts would be updated for the host going forward unless someone manually cancels the build.
Expected results:
No registration method ( including GRT ) should depend on access of port 80 , whether it's satellite or capsule.
Additional info:
As explained in https://bugzilla.redhat.com/show_bug.cgi?id=2247445, we don't have this issue for external capsules, as there we use port 8000 to hit the `/unattended/built` endpoint
Perhaps we can make it mandatory to enable templates capsule in Satellite as well and make use of port 8000 instead or develop some other solution that can work over port 443.
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.