Bug #14750: foreman proxy still running on port 8000 needlessly. - Katello - Foreman

Actions

Copy link

Bug #14750

closed

foreman proxy still running on port 8000 needlessly.

Added by Ondřej Pražák over 8 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Ondřej Pražák

Category:

Target version:

Katello 3.1.0

Difficulty:

Triaged:

Bugzilla link:

1248665

Pull request:

https://github.com/Katello/katello-installer/pull/328

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1248665
Description of problem:

Please see https://bugzilla.redhat.com/show_bug.cgi?id=1237092

templates on the default server were turned off, which is expected. However, foreman-proxy is still listening on port 8000.

Version-Release number of selected component (if applicable):

Snap 15

Steps to Reproduce:
1. Install satellite
2. `lsof -i :8000`

Actual results:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ruby 23526 foreman-proxy 9u IPv4 108908 0t0 TCP *:irdmi (LISTEN)

Expected results:

foreman-proxy should not be listening needlessly on port 8000
Additional info:

Actions

Copy link

Updated by Dominic Cleal over 8 years ago

Status changed from New to Need more information

Can you provide more information? If the foreman_proxy http/http_port parameters are enabled then it will be running on HTTP. What did you set them to?

Actions

Copy link

Updated by Ondřej Pražák over 8 years ago

Dominic Cleal wrote:

Can you provide more information? If the foreman_proxy http/http_port parameters are enabled then it will be running on HTTP. What did you set them to?

I did not touch them at all. From the BZ ticket I gathered the proxy is running on http 8000 by default and it should not. I reproduced with 'steps to reproduce' and found out the :http_port in /etc/foreman-proxy/settings.yml is not commented out.

Actions

Copy link

Updated by Dominic Cleal over 8 years ago

Project changed from Installer to Katello
Status changed from Need more information to New

Moving this to Katello then, perhaps it enables the parameter - foreman-installer does not.

Actions

Copy link

Updated by Ewoud Kohl van Wijngaarden over 8 years ago

I think https://github.com/Katello/katello-installer/blob/730ba848bd6532a8abd65e9001fd470a031cefa7/config/capsule.migrations/160120212700-foreman-proxy.rb#L31 is the reason.

Actions

Copy link

Updated by Ondřej Pražák over 8 years ago

Thanks for a hint.

Actions

Copy link

Updated by Christian Ehart over 8 years ago

Small Recommendation, would it not be better to listen on other port like "9000" instead of "9090"? Of course I can do it manually, but a predefined setup would be better...

Reason: Cockpit uses already the port 9090, see https://groups.google.com/forum/#!searchin/foreman-users/9090/foreman-users/QEAQjGs1exQ/temrvqXFBQAJ

more details via Google: https://www.google.at/search?q=cockpit+9090&ie=utf-8&oe=utf-8&gws_rd=cr&ei=7RAZV5CPLKvEgAaokproBw

Actions

Copy link

Updated by Ondřej Pražák over 8 years ago

Christian Ehart wrote:

Small Recommendation, would it not be better to listen on other port like "9000" instead of "9090"? Of course I can do it manually, but a predefined setup would be better...

Reason: Cockpit uses already the port 9090, see https://groups.google.com/forum/#!searchin/foreman-users/9090/foreman-users/QEAQjGs1exQ/temrvqXFBQAJ

more details via Google: https://www.google.at/search?q=cockpit+9090&ie=utf-8&oe=utf-8&gws_rd=cr&ei=7RAZV5CPLKvEgAaokproBw

If there is a clash then maybe it would be better to change it. Could you file a new issue?

Actions

Copy link