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.

The bug 1643183 was marked CLOSED ERRATA, resolved in Satellite 6.4 through foreman-installer-1.18.0.3-1 (https://access.redhat.com/errata/RHBA-2019:0345).
This package provides the Puppet module foreman_proxy version 7.2.3

However, the same bug appears again in Satellite 6.5 with foreman-installer-1.20.0-2. Here, the foreman_proxy Puppet module bumps to version 9.0.0

It can be seen from the following GitHub pull request https://github.com/theforeman/puppet-foreman_proxy/pull/466 and associated commit https://github.com/theforeman/puppet-foreman_proxy/commit/0940a056ac2bf0cf4c5049d4acb706a74f07f5d0 that the problem was only fixed upstream starting from version 10.0.0 of the foreman_proxy Puppet module.

Upstream bug assigned to egolov

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25460 has been resolved.

Hi Fabien,

Thanks for raising the bugzilla.

I have confirmed that the fix referenced by upstream redmine 25460 is included in the current Satellite 6.6 beta.  Since this will becoming with the next release, I am going to close the bugzilla.

Reference from an early 6.6 install:

File: /usr/share/foreman-installer/modules/foreman_proxy/manifests/params.pp

...
...
150   # Enable listening on http
151   if $::osfamily == 'RedHat' and versioncmp($::operatingsystemmajrelease, '7') <= 0 and has_key($facts, 'ipaddress6') {

https://access.redhat.com/solutions/5045841 documents the correct way to disable IPv6 when using Satellite. This has been adopted in April/May so is more recent. It is recommended to follow this procedure.

Alternatively the --foreman-proxy-bind-host parameter can be used to override the listen address.