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:
Foreman service expects 19090
But remote execution provides 9999

As you can see in foreman-tail and remote_execution/cockpit.pp
foreman-tail:
Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:9999 (*) 

This bz is connected to this PR - https://github.com/theforeman/puppet-foreman/pull/768

PR is merged, but it do not drop into snap3 


Version-Release number of selected component (if applicable):
sat 6.7 snap 3

Expected results:
Get PR into downstream.

Moving to post as PR is already merged, just forgotten.

VERIFIED.

@Satellite 6.7.0 Snap4
foreman-installer-1.24.0-0.7.RC3.el7sat.noarch

by following manual steps:

# cat /etc/httpd/conf.d/05-foreman-ssl.d/cockpit.conf
...

  RewriteEngine On
  RewriteCond %{HTTP:Upgrade} =websocket [NC]
  RewriteRule /webcon/(.*)           ws://127.0.0.1:19090/webcon/$1 [P]
  RewriteCond %{HTTP:Upgrade} !=websocket [NC]
  RewriteRule /webcon/(.*)           http://127.0.0.1:19090/webcon/$1 [P]

>>> apache rewrite rules are configured to use 19090/tcp

# netstat -plnt | grep cockpit[-]ws
tcp        0      0 127.0.0.1:19090         0.0.0.0:*               LISTEN      8916/cockpit-ws     

>>> foreman-cockpit service is listening on the same port 19090/tcp

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, 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:1454