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