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.

Bug 1789006

Summary: Smart proxy dynflow core listens on 0.0.0.0
Product: Red Hat Satellite Reporter: Adam Ruzicka <aruzicka>
Component: InstallationAssignee: Ewoud Kohl van Wijngaarden <ekohlvan>
Status: CLOSED ERRATA QA Contact: Devendra Singh <desingh>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: egolov, zhunting
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-installer-2.0.0-0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 12:59:52 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Ruzicka 2020-01-08 15:03:51 UTC 
We may want to use localhost to make it bind to both v4 and v6 sockets.
Comment 1 Adam Ruzicka 2020-01-08 15:03:56 UTC 
Created from redmine issue https://projects.theforeman.org/issues/28681
Comment 7 Zach Huntington-Meath 2020-01-09 14:14:07 UTC 
*** Bug 1789007 has been marked as a duplicate of this bug. ***
Comment 8 Bryan Kearney 2020-01-14 15:06:12 UTC 
Upstream bug assigned to ekohlvan
Comment 9 Bryan Kearney 2020-01-14 15:06:14 UTC 
Upstream bug assigned to ekohlvan
Comment 10 Bryan Kearney 2020-01-15 15:05:14 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28681 has been resolved.
Comment 12 Devendra Singh 2020-07-14 15:53:44 UTC 
Verification points:

Satellite version: 6.8 Snap8

1- foreman-installer version

# rpm -q foreman-installer
foreman-installer-2.1.0-1.el7sat.noarch

2. Smart_proxy_dynflow_core.pid listen on all ip4 and ipv6 addresses.

# ps -aef|grep foreman-proxy
foreman+ 10974     1  0 Jul13 ?        00:00:56 ruby /usr/bin/smart_proxy_dynflow_core -d -p /var/run/foreman-proxy/smart_proxy_dynflow_core.pid
foreman+ 36992     1  0 Jul13 ?        00:00:04 ruby /usr/share/foreman-proxy/bin/smart-proxy --no-daemonize

#  sudo netstat -lnp|grep 36992
tcp        0      0 0.0.0.0:9090            0.0.0.0:*               LISTEN      36992/ruby          
tcp6       0      0 :::9090                 :::*                    LISTEN      36992/ruby          
#  sudo netstat -lnp|grep 10974
tcp        0      0 0.0.0.0:8008            0.0.0.0:*               LISTEN      10974/ruby          
tcp6       0      0 :::8008                 :::*                    LISTEN      10974/ruby
Comment 13 Devendra Singh 2020-07-14 16:22:58 UTC 
There was a typo in Comment12 step2, Smart_proxy_dynflow_core.service listen on all ipv4 and ipv6 addresses instead of Smart_proxy_dynflow_core.pid.
Comment 16 errata-xmlrpc 2020-10-27 12:59:52 UTC 
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.8 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-2020:4366