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:
The change in https://github.com/theforeman/puppet-foreman_proxy_content/commit/76e2a6852d1d2ca33935ccf8a6ab69992c32ec1d did set rhsm_port to 443 unconditionally, which is fine for RHSM, as the same commit also configures a reverse proxy on smartproxy:443/rhsm to map to katello:443/rhsm.

However, this breaks bootstrap as it expects (wrongfully, but it does) to be able to talk the the API on the same port as RHSM (which isn’t true anymore):

https://github.com/Katello/katello-client-bootstrap/blob/1027a2ed474ce2003ccc7062db3abb497c7b286d/bootstrap.py#L1012-L1019

Version-Release number of selected component (if applicable):
katello-client-bootstrap-1.7.7
foreman-installer-3.1.2

How reproducible:
100%

Steps to Reproduce:
1. setup a satellite and a capsule
2. try to use bootstrap.py against the capsule without passing "--skip foreman"

Actual results:
An error occurred: HTTP Error 404: Not Found
url: https://smartproxyfqdn:443/api/v2/hostgroups/?search=title%3D"centos7"
code: 404
error: HTTP Error 404: Not Found

Expected results:
bootstrap works

Additional info:
Originally reported upstream in https://community.theforeman.org/t/smart-proxy-missing-api-after-foreman-3-1-2-katello-4-3-upgrade/27717

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 (Moderate: Satellite 6.11 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:5498